Method and apparatus for configuring service

ABSTRACT

This application provides a method and an apparatus for configuring a service, which help to implement automatic configuration of a service and improve efficiency. The method provided in this application includes: obtaining, by an NaaS device, a contract of a service, where the contract includes identifier information and a condition, the identifier information is used to identify a first device group, the first device group includes a device that provides the service, and the condition is a communication requirement corresponding to the service; obtaining, by the NaaS device, information about a network device group according to the identifier information and the condition; obtaining, by the NaaS device, a first forwarding rule according to the condition, where the first forwarding rule corresponds to the network device group; and sending, by the NaaS device, the first forwarding rule and the information about the network device group to a controller.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/449,603, filed on Mar. 3, 2017, which is a continuation ofInternational Application No. PCT/CN2015/087578, filed on Aug. 20, 2015,which claims priority to Chinese Patent Application No. 201410453604.1,filed on Sep. 5, 2014. All of the aforementioned patent applications arehereby incorporated by reference in their entireties.

TECHNICAL FIELD

The present application relates to the field of communicationstechnologies, and specifically, to a method and an apparatus forconfiguring a service.

BACKGROUND

A software-defined networking (SDN) is a new-type network architecture,and may be roughly divided into the following three layers: anupper-layer application, such as a cloud (cloud) or an over-the-top(OTT); an intermediate-layer controller (Controller); and a bottom-layerphysical network device, such as a switch or a router.

Currently, when a bottom-layer physical network device for implementinga specific service is configured for an upper-layer application, networkmanagement personnel need to obtain a service involved in theupper-layer application and a service requirement, and further need toobtain functions that can be implemented by physical network devices.The network management personnel may select, according to the functionsthat can be implemented by the physical network devices, a physicalnetwork device matching the service requirement. The network managementpersonnel configure the service for the selected physical networkdevice. In this way, service configuration for a network device isrelatively complex, and work efficiency is relatively low. Ifupper-layer applications have more types and enhanced functions, serviceconfiguration for a network device becomes more complex, and workefficiency is reduced.

SUMMARY

A method and an apparatus for configuring a service that are provided inembodiments of the present application help to implement automaticconfiguration of a service and improve efficiency.

Therefore, the following technical solutions are provided in theembodiments of the present application:

According to a first aspect, a method for configuring a service isprovided, including:

obtaining, by an NaaS device, a contract of a service, where thecontract includes identifier information and a condition, the identifierinformation is used to identify a first device group, the first devicegroup includes a device that provides the service, and the condition isa communication requirement corresponding to the service;

obtaining, by the NaaS device, information about a network device groupaccording to the identifier information and the condition;

obtaining, by the NaaS device, a first forwarding rule according to thecondition, where the first forwarding rule corresponds to the networkdevice group; and

sending, by the NaaS device, the first forwarding rule and theinformation about the network device group to a controller.

In a first possible implementation manner of the first aspect, theidentifier information is a first identifier, the condition is acommunication requirement for accessing a device group identified by thefirst identifier, and the obtaining, by the NaaS device, informationabout a network device group according to the identifier information andthe condition includes:

obtaining, by the NaaS device, a second device group corresponding tothe first identifier, where the second device group includes a firstdevice, and the first device is a device that meets the communicationrequirement;

selecting, by the NaaS device, the first device from the second devicegroup according to the communication requirement for accessing thedevice group identified by the first identifier; and

obtaining, by the NaaS device, information about the first device, wherethe information about the first device includes an identifier of thefirst device and an interface of the first device.

With reference to the first possible implementation manner of the firstaspect, a second possible implementation manner of the first aspect isfurther provided, where the obtaining, by the NaaS device, a firstforwarding rule according to the condition includes:

obtaining, by the NaaS device, a first match field and a first actionfrom the condition, where the first match field corresponds to thecommunication requirement for accessing the device group identified bythe first identifier, and the first action corresponds to an accessoperation; and

generating, by the NaaS device, a forwarding rule of the first deviceaccording to the first match field and the first action.

With reference to the second possible implementation manner of the firstaspect, a third possible implementation manner of the first aspect isfurther provided, where the obtaining, by the NaaS device, a firstforwarding rule according to the condition further includes:

performing, by the NaaS device, a conflict check on the forwarding ruleof the first device and a second forwarding rule, where the secondforwarding rule is a forwarding rule that is already configured on thefirst device; and

if the forwarding rule of the first device conflicts with the secondforwarding rule, obtaining, by the NaaS device, a calibrated forwardingrule of the first device.

With reference to the second or the third possible implementation mannerof the first aspect, a fourth possible implementation manner of thefirst aspect is further provided, where the obtaining, by the NaaSdevice, a first forwarding rule according to the condition furtherincludes:

determining, by the NaaS device, whether the forwarding rule of thefirst device and a forwarding rule of a second device in the seconddevice group form a transmission abnormality; and

if the forwarding rule of the first device and the forwarding rule ofthe second device in the second device group form a transmissionabnormality, obtaining, by the NaaS device, a third forwarding rule,where the third forwarding rule is a calibrated forwarding rule of thesecond device.

In a fifth possible implementation manner of the first aspect, theidentifier information includes a second identifier and a thirdidentifier, the condition is a requirement on communication between adevice group identified by the second identifier and a device groupidentified by the third identifier, and the obtaining, by the NaaSdevice, information about a network device group according to theidentifier information and the condition includes:

obtaining, by the NaaS device, a third device group corresponding to thesecond identifier and a fourth device group corresponding to the thirdidentifier, where the third device group includes a device used as asource node, and the fourth device group includes a device used as adestination node;

selecting, by the NaaS device, a third device from the third devicegroup according to the requirement on communication between the devicegroup identified by the second identifier and the device groupidentified by the third identifier, where the third device is the sourcenode;

selecting, by the NaaS device, a fourth device from the fourth devicegroup according to the requirement on communication between the devicegroup identified by the second identifier and the device groupidentified by the third identifier, where the fourth device is thedestination node;

obtaining, by the NaaS device, information about the third device andinformation about the fourth device, where the information about thethird device includes an identifier of the third device and an interfaceof the third device, and the information about the fourth deviceincludes an identifier of the fourth device and an interface of thefourth device.

With reference to the fifth possible implementation manner of the firstaspect, a sixth possible implementation manner of the first aspect isfurther provided, where the obtaining, by the NaaS device, a firstforwarding rule according to the condition includes:

obtaining, by the NaaS device, a second match field and a second actionfrom the condition, where the second match field corresponds to therequirement on communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier, and the second action corresponds to communication betweenthe device group identified by the second identifier and the devicegroup identified by the third identifier; and

generating, by the NaaS device, a forwarding rule of the third deviceand a forwarding rule of the fourth device according to the second matchfield and the second action.

With reference to the sixth possible implementation manner of the firstaspect, a seventh possible implementation manner of the first aspect isfurther provided, where the obtaining, by the NaaS device, a firstforwarding rule according to the condition further includes:

performing, by the NaaS device, a conflict check on the forwarding ruleof the third device and a fourth forwarding rule, where the fourthforwarding rule is a forwarding rule that is already configured on thethird device; and

if the forwarding rule of the third device conflicts with the fourthforwarding rule, obtaining, by the NaaS device, a calibrated forwardingrule of the third device.

With reference to the sixth or the seventh possible implementationmanner of the first aspect, an eighth possible implementation manner ofthe first aspect is further provided, where the obtaining, by the NaaSdevice, a first forwarding rule according to the condition furtherincludes:

performing, by the NaaS device, a conflict check on the forwarding ruleof the fourth device and a fifth forwarding rule, where the fifthforwarding rule is a forwarding rule that is already configured on thefourth device; and

if the forwarding rule of the fourth device conflicts with the fifthforwarding rule, obtaining, by the NaaS device, a calibrated forwardingrule of the fourth device.

With reference to any one of the sixth to the eighth possibleimplementation manners of the first aspect, a ninth possibleimplementation manner of the first aspect is further provided, where theobtaining, by the NaaS device, a first forwarding rule according to thecondition further includes:

determining, by the NaaS device, whether the forwarding rule of thethird device and a forwarding rule of a fifth device in the third devicegroup form a transmission abnormality; and

if the forwarding rule of the third device and the forwarding rule ofthe fifth device in the third device group form a transmissionabnormality, obtaining, by the NaaS device, a sixth forwarding rule,where the sixth forwarding rule is a calibrated forwarding rule of thefifth device.

With reference to any one of the sixth to the ninth possibleimplementation manners of the first aspect, a tenth possibleimplementation manner of the first aspect is further provided, where theobtaining, by the NaaS device, a first forwarding rule according to thecondition further includes:

determining, the NaaS device, whether the forwarding rule of the fourthdevice and a forwarding rule of a sixth device in the fourth devicegroup form a transmission abnormality; and

if the forwarding rule of the fourth device and the forwarding rule ofthe sixth device in the fourth device group form a transmissionabnormality, obtaining, by the NaaS device, a seventh forwarding rule,where the seventh forwarding rule is a calibrated forwarding rule of thesixth device.

In an eleventh possible implementation manner of the first aspect, theidentifier information is a fourth identifier and a fifth identifier,the condition is a communication requirement for a device groupidentified by the fourth identifier to join a multicast group identifiedby the fifth identifier, and the obtaining, by the NaaS device,information about a network device group according to the identifierinformation and the condition includes:

obtaining, by the NaaS device, a fifth device group corresponding to thefourth identifier, where the fifth device group includes a device thatcommunicates with a device identified by the fourth identifier;

selecting, by the NaaS device, a seventh device from the fifth devicegroup according to the communication requirement for the device groupidentified by the fourth identifier to join the multicast groupidentified by the fifth identifier, where the seventh devicecommunicates with the device group identified by the fourth identifier;and

obtaining, by the NaaS device, information about the seventh device,where the information about the seventh device includes an identifier ofthe seventh device and an interface of the seventh device.

With reference to the eleventh possible implementation manner of thefirst aspect, a twelfth possible implementation manner of the firstaspect is further provided, where the obtaining, by the NaaS device, afirst forwarding rule according to the condition includes:

obtaining, by the NaaS device, a third match field and a third actionfrom the condition, where the third match field corresponds to thecommunication requirement for the device group identified by the fourthidentifier to join the multicast group identified by the fifthidentifier, and the third action corresponds to a multicast operation;and

generating, by the NaaS device, a forwarding rule of the seventh deviceaccording to the third match field and the third action.

With reference to the twelfth possible implementation manner of thefirst aspect, a thirteenth possible implementation manner of the firstaspect is further provided, where the obtaining, by the NaaS device, afirst forwarding rule according to the condition further includes:

performing, by the NaaS device, a conflict check on the forwarding ruleof the seventh device and an eighth forwarding rule, where the eighthforwarding rule is a forwarding rule that is already configured on theseventh device; and

if the forwarding rule of the seventh device conflicts with the eighthforwarding rule, obtaining, by the NaaS device, a calibrated forwardingrule of the seventh device.

With reference to the twelfth or the thirteenth possible implementationmanner of the first aspect, a fourteenth possible implementation mannerof the first aspect is further provided, where the obtaining a firstforwarding rule further includes:

determining, by the NaaS device, whether the forwarding rule of theseventh device and a forwarding rule of an eighth device in the fifthdevice group form a transmission abnormality; and

if a transmission abnormality is formed, obtaining, by the NaaS device,a ninth forwarding rule, where the ninth forwarding rule is a calibratedforwarding rule of the eighth device.

With reference to any one of the first aspect or any possibleimplementation manner of the first aspect, a fifteenth possibleimplementation manner of the first aspect is further provided, where themethod further includes:

obtaining, by the NaaS device, a detection packet according to the firstforwarding rule and the information about the network device group,where the detection packet is used to obtain a detection result from thenetwork device group, and the detection result is a result obtained bydetecting communication that is performed by the network device groupaccording to the first forwarding rule;

sending, by the NaaS device, the detection packet to the controller;

receiving, by the NaaS device, the detection result sent by thecontroller; and

if the detection result meets a preset condition, adjusting, by the NaaSdevice, the contract according to the detection result.

In a sixteenth possible implementation manner of the first aspect, thecontract further includes a type of the service, and the type of theservice is access, routing, or multicast.

According to a second aspect, an apparatus for configuring a service isprovided, including:

a contract obtaining unit, configured to obtain a contract of a service,where the contract includes identifier information and a condition, theidentifier information is used to identify a first device group, thefirst device group includes a device that provides the service, and thecondition is a communication requirement corresponding to the service;

a network device group obtaining unit, configured to obtain informationabout a network device group according to the identifier information andthe condition;

a rule obtaining unit, configured to obtain a first forwarding ruleaccording to the condition, where the first forwarding rule correspondsto the network device group; and

a first sending unit, configured to send the first forwarding rule andthe information about the network device group to a controller.

In a first possible implementation manner of the second aspect, theidentifier information is a first identifier, and the condition is acommunication requirement for accessing a device group identified by thefirst identifier;

the network device group obtaining unit is specifically configured toobtain a second device group corresponding to the first identifier,where the second device group includes a first device, and the firstdevice is a device that meets the communication requirement;

the network device group obtaining unit is specifically configured toselect the first device from the second device group according to thecommunication requirement for accessing the device group identified bythe first identifier; and

the network device group obtaining unit is specifically configured toobtain information about the first device, where the information aboutthe first device includes an identifier of the first device and aninterface of the first device.

With reference to the first possible implementation manner of the secondaspect, a second possible implementation manner of the second aspect isfurther provided, where the rule obtaining unit is specificallyconfigured to obtain a first match field and a first action from thecondition, where the first match field corresponds to the communicationrequirement for accessing the device group identified by the firstidentifier, and the first action corresponds to an access operation; and

the rule obtaining unit is specifically configured to generate aforwarding rule of the first device according to the first match fieldand the first action.

With reference to the second possible implementation manner of thesecond aspect, a third possible implementation manner of the secondaspect is further provided, where the rule obtaining unit is furtherconfigured to perform a conflict check on the forwarding rule of thefirst device and a second forwarding rule, where the second forwardingrule is a forwarding rule that is already configured on the firstdevice; and

if the forwarding rule of the first device conflicts with the secondforwarding rule, the rule obtaining unit is configured to obtain acalibrated forwarding rule of the first device.

With reference to the second or the third possible implementation mannerof the second aspect, a fourth possible implementation manner of thesecond aspect is further provided, where the rule obtaining unit isfurther configured to determine whether the forwarding rule of the firstdevice and a forwarding rule of a second device in the second devicegroup form a transmission abnormality; and

if the forwarding rule of the first device and the forwarding rule ofthe second device in the second device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a thirdforwarding rule, where the third forwarding rule is a calibratedforwarding rule of the second device.

In a fifth possible implementation manner of the second aspect, theidentifier information includes a second identifier and a thirdidentifier, and the condition is a requirement on communication betweena device group identified by the second identifier and a device groupidentified by the third identifier;

the network device group obtaining unit is specifically configured toobtain a third device group corresponding to the second identifier and afourth device group corresponding to the third identifier, where thethird device group includes a device used as a source node, and thefourth device group includes a device used as a destination node;

the network device group obtaining unit is specifically configured toselect a third device from the third device group according to therequirement on communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier, where the third device is the source node;

the network device group obtaining unit is specifically configured toselect a fourth device from the fourth device group according to therequirement on communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier, where the fourth device is the destination node; and

the network device group obtaining unit is specifically configured toobtain information about the third device and information about thefourth device, where the information about the third device includes anidentifier of the third device and an interface of the third device, andthe information about the fourth device includes an identifier of thefourth device and an interface of the fourth device.

With reference to the fifth possible implementation manner of the secondaspect, a sixth possible implementation manner of the second aspect isfurther provided, where the rule obtaining unit is specificallyconfigured to obtain a second match field and a second action from thecondition, where the second match field corresponds to the requirementon communication between the device group identified by the secondidentifier and the device group identified by the third identifier, andthe second action corresponds to communication between the device groupidentified by the second identifier and the device group identified bythe third identifier; and

the rule obtaining unit is specifically configured to generate aforwarding rule of the third device and a forwarding rule of the fourthdevice according to the second match field and the second action.

With reference to the sixth possible implementation manner of the secondaspect, a seventh possible implementation manner of the second aspect isfurther provided, where the rule obtaining unit is further configured toperform a conflict check on the forwarding rule of the third device anda fourth forwarding rule, where the fourth forwarding rule is aforwarding rule that is already configured on the third device; and

if the forwarding rule of the third device conflicts with the fourthforwarding rule, the rule obtaining unit is configured to obtain acalibrated forwarding rule of the third device.

With reference to the sixth or the seventh possible implementationmanner of the second aspect, an eighth possible implementation manner ofthe second aspect is further provided, where the rule obtaining unit isfurther configured to perform a conflict check on the forwarding rule ofthe fourth device and a fifth forwarding rule, where the fifthforwarding rule is a forwarding rule that is already configured on thefourth device; and

if the forwarding rule of the fourth device conflicts with the fifthforwarding rule, the rule obtaining unit is configured to obtain acalibrated forwarding rule of the fourth device.

With reference to any one of the sixth to the eighth possibleimplementation manners of the second aspect, a ninth possibleimplementation manner of the second aspect is further provided, wherethe rule obtaining unit is further configured to determine whether theforwarding rule of the third device and a forwarding rule of a fifthdevice in the third device group form a transmission abnormality; and

if the forwarding rule of the third device and the forwarding rule ofthe fifth device in the third device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a sixthforwarding rule, where the sixth forwarding rule is a calibratedforwarding rule of the fifth device.

With reference to any one of the sixth to the ninth possibleimplementation manners of the second aspect, a tenth possibleimplementation manner of the second aspect is further provided, wherethe rule obtaining unit is further configured to determine whether theforwarding rule of the fourth device and a forwarding rule of a sixthdevice in the fourth device group form a transmission abnormality; and

if the forwarding rule of the fourth device and the forwarding rule ofthe sixth device in the fourth device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a seventhforwarding rule, where the seventh forwarding rule is a calibratedforwarding rule of the sixth device.

In an eleventh possible implementation manner of the second aspect, theidentifier information is a fourth identifier and a fifth identifier,and the condition is a communication requirement for a device groupidentified by the fourth identifier to join a multicast group identifiedby the fifth identifier;

the network device group obtaining unit is specifically configured toobtain a fifth device group corresponding to the fourth identifier,where the fifth device group includes a device that communicates with adevice identified by the fourth identifier;

the network device group obtaining unit is specifically configured toselect a seventh device from the fifth device group according to thecommunication requirement for the device group identified by the fourthidentifier to join the multicast group identified by the fifthidentifier, where the seventh device communicates with the device groupidentified by the fourth identifier; and

the network device group obtaining unit is specifically configured toobtain information about the seventh device, where the information aboutthe seventh device includes an identifier of the seventh device and aninterface of the seventh device.

With reference to the eleventh possible implementation manner of thesecond aspect, a twelfth possible implementation manner of the secondaspect is further provided, where the rule obtaining unit isspecifically configured to obtain a third match field and a third actionfrom the condition, where the third match field corresponds to thecommunication requirement for the device group identified by the fourthidentifier to join the multicast group identified by the fifthidentifier, and the third action corresponds to a multicast operation;and

the rule obtaining unit is specifically configured to generate aforwarding rule of the seventh device according to the third match fieldand the third action.

With reference to the twelfth possible implementation manner of thesecond aspect, a thirteenth possible implementation manner of the secondaspect is further provided, where the rule obtaining unit is furtherconfigured to perform a conflict check on the forwarding rule of theseventh device and an eighth forwarding rule, where the eighthforwarding rule is a forwarding rule that is already configured on theseventh device; and

if the forwarding rule of the seventh device conflicts with the eighthforwarding rule, the rule obtaining unit is configured to obtain acalibrated forwarding rule of the seventh device.

With reference to the twelfth or the thirteenth possible implementationmanner of the second aspect, a fourteenth possible implementation mannerof the second aspect is further provided, where the rule obtaining unitis further configured to determine whether the forwarding rule of theseventh device and a forwarding rule of an eighth device in the fifthdevice group form a transmission abnormality; and

if the forwarding rule of the seventh device and the forwarding rule ofthe eighth device in the fifth device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a ninthforwarding rule, where the ninth forwarding rule is a calibratedforwarding rule of the eighth device.

With reference to any one of the second aspect or any possibleimplementation manner of second aspect, a fifteenth possibleimplementation manner of the second aspect is further provided, wherethe apparatus further includes:

a detection packet obtaining unit, configured to obtain a detectionpacket according to the first forwarding rule and the information aboutthe network device group, where the detection packet is used to obtain adetection result from the network device group, and the detection resultis a result obtained by detecting communication that is performed by thenetwork device group according to the first forwarding rule;

a second sending unit, configured to send the detection packet to thecontroller;

a receiving unit, configured to receive the detection result sent by thecontroller; and

an adjustment unit, configured to adjust the contract according to thedetection result when the detection result meets a preset condition.

In a sixteenth possible implementation manner of the second aspect, thecontract further includes a type of the service, and the type of theservice is access, routing, or multicast.

For the method and apparatus for configuring a service in theembodiments of the present application, an NaaS device obtains acontract corresponding to a communication requirement of a user, theNaaS device then may automatically convert a condition in the contractinto a first forwarding rule and select, according to identifierinformation and the condition, information about a network device groupthat meets a requirement of the contract, and the NaaS device sends thefirst forwarding rule and the information about the network device groupto a controller. The method and apparatus for configuring a service inthe embodiments of the present application not only help to implementautomatic configuration of a service, but also help to improveefficiency of configuring a service.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentapplication more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments. Theaccompanying drawings in the following description show merely someembodiments of the present application, and a person of ordinary skillin the art may still derive other drawings from these accompanyingdrawings without creative efforts.

FIG. 1 is a flowchart of a method for configuring a service according toan embodiment of the present application;

FIG. 2 is a schematic diagram of a network architecture according to anembodiment of the present application;

FIG. 3 is a schematic diagram of a scenario of implementing an accessfiltering service according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a scenario of implementing a bandwidthcommunication requirement service according to an embodiment of thepresent application;

FIG. 5 is a schematic diagram of a scenario of implementing a VPNservice according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a scenario of implementing a multicastservice according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an apparatus for configuring a serviceaccording to an embodiment of the present application; and

FIG. 8 is a schematic diagram of an apparatus for configuring a serviceaccording to an embodiment of the present application.

DESCRIPTION OF EMBODIMENTS

In order to make a person skilled in the art better understand thesolutions in the present application, the following further describesthe embodiments of the present application in detail with reference toaccompanying drawings and implementation manners.

A method for configuring a service, which is provided in the embodimentsof the present application, is applicable to a network as a service(NaaS) device. The NaaS device may be a device having an NaaS function.For example, the NaaS device may be a network device that communicateswith a Controller, the NaaS device may be a Controller integrated withthe NaaS function, or the NaaS function of the NaaS device may beimplemented by multiple different network devices together, that is, theNaaS function is divided and distributed to the multiple differentnetwork devices, so as to implement the NaaS function in a distributedmanner. In the embodiments of the present application, a form in whichan NaaS device exists in a network is not specifically limited. In thefollowing embodiments of the present application, an NaaS device is usedas an example for description, and details of different forms of NaaSdevices are not described.

Referring to FIG. 1, a method for configuring a service, which isprovided in an embodiment of the present application, may include:

101: An NaaS device obtains a contract of a service, where the contractincludes identifier information and a condition, the identifierinformation is used to identify a first device group, the first devicegroup includes a device that provides the service, and the condition isa communication requirement corresponding to the service.

For example, the service (service) is a service required by a user. Thecontract may be used to denote a condition for communication between twouser groups (USG). The contract may be denoted as <USGx, USGy, servicetype, service contract>, where the USGx and the USGy may be theidentifier information included in the contract; the service type is atype of the service, where the service type is optional, and the servicetype may be used to determine a type of the contract; and the servicecontract may be the condition included in the contract. In thisembodiment of the present application, the contract may be an accesscontract, a routing contract, or a multicast contract. For example, theaccess contract may be denoted as <USG1, USG outside, access, accesscontract>, the routing contract may be denoted as <USG2, USG3, routing,routing contract>, and the multicast contract may be denoted as <USG4,USG multicast, multicast, multicast contract>, where a form of thecontract is not limited to the foregoing several forms.

For example, one or more devices having a same communication requirementmay belong to one device group, or one or more devices having a samecommunication capability may belong to one device group. In thisembodiment of the present application, the device group may be referredto as a USG. The USG may be further referred to as an endpoint group(EPG). Referring to a diagram of a network architecture shown in FIG. 2,an NaaS device may communicate with a user and a Controller separately.The NaaS device may obtain the contract of the service according toinformation that is input by the user. The information that is input bythe user may include: a condition and identifier information. The NaaSdevice may receive a contract that is input by the user in a manner of acommand line, a Web interface, or the like. Alternatively, the NaaSdevice may further predefine description models of some contracts, andthe NaaS device may obtain a contract according to a parameter that isinput by the user and a predefined description model. In this embodimentof the present application, a specific manner in which the NaaS deviceobtains a contract may be not specifically limited.

For example, the access contract may be used to denote a condition for adevice group identified by the USG1 to access a device group identifiedby the USG2. The device group identified by the USG1 is a set of deviceshaving a same communication requirement, and the device group identifiedby the USG2 is a set of devices that can meet a communicationrequirement of the USG1. The device group identified by the USG2includes at least one device that can meet the communication requirementof the USG1. The access contract obtained by the NaaS device may be<USG2, access contract>, <USG2, access, access contract>, <USG2, USG1,access contract>, <USG2, USG outside, access, access contract>, <USG2,USG1, access, access contract>, or a like form, and details are notdescribed herein example by example. The USG outside may denote a devicegroup that accesses the USG2 from outside. If the access contract is<USG2, access contract> or <USG2, access, access contract>, theidentifier information includes the USG2. If the access contract is<USG2, USG1, access contract> or <USG2, USG1, access, access contract>,the identifier information includes the USG2 and the USG1. If the accesscontract is <USG2, USG outside, access, access contract>, the identifierinformation includes the USG2 and the USG outside. The access is used toidentify that the contract is an access contract. The access contractincludes a condition in the access contract, that is, the accesscontract includes a communication requirement for accessing the USG2 bythe USG1, for example, the communication requirement for accessing theUSG2 may include: a port number being 80, a protocol type beingTransmission Control Protocol (TCP), and the like.

For example, the routing contract may be used to denote a requirement oncommunication between a device group identified by the USG3 and a devicegroup identified by the USG4. The routing contract obtained by the NaaSdevice may be <USG3, USG4, routing contract> or <USG3, USG4, routing,routing contract>. The USG3 and the USG4 are identifier informationincluded in the routing contract, and the routing is used to identifythat the contract is a routing contract. The routing contract includes acondition in the routing contract, that is, the routing contractincludes the requirement on communication between the device groupidentified by the USG3 and the device group identified by the USG4. Forexample, the communication requirement included in the routing contractmay be: a bandwidth being 10 G. A direction of routing between the USG3and the USG4 may be further set in the routing contract. For example, itis set that the routing is unidirectional or bidirectional. If therouting is unidirectional, the routing contract may include arequirement on communication between a source node of the routing and adestination node of the routing. If the routing is bidirectional, therouting contract may include working modes, such as a simplex mode, ahalf-duplex mode, or a duplex mode, of two devices that provide therouting function.

For example, the multicast contract may be used to denote a multicastcommunication requirement for a USG5 to join USG multicast. A devicegroup identified by the USG5 is a set of devices that request to jointhe USG multicast, and the USG multicast is used to identify a multicastgroup. The multicast contract obtained by the NaaS device may be <USG5,USG multicast, multicast contract> or <USG5, USG multicast, multicast,multicast contract>. The USG5 and the USG multicast are identifierinformation included in the multicast contract, the USG5 may be used toidentify a multicast source or a multicast receiving device, themulticast is used to identify that the contract is a multicast contract,and the multicast contract includes a condition in the multicastcontract, that is, the multicast contract includes the multicastcommunication requirement for the device group identified by the USG5 tojoin the multicast group identified by the USG multicast. If the USGmulticast is used to denote a multicast group whose address is225.1.1.1, the communication requirement included in the multicastcontract may be that the device group identified by the USG5 requests tojoin the multicast group 225.1.1.1.

102: The NaaS device obtains information about a network device groupaccording to the identifier information and the condition.

For example, if the contract is an access contract or a routingcontract, the NaaS device may obtain a candidate device group accordingto the identifier information, and the NaaS device may obtain thenetwork device group from the candidate device group according to thecondition. Alternatively, the NaaS device may directly obtain a locallysaved candidate device group, and the NaaS device may obtain the networkdevice group from the candidate device group according to the conditionand the identifier information. The candidate device group includes anetwork device that can meet the condition. If the contract is amulticast contract, the NaaS device may obtain the network device groupaccording to the identifier information and the condition.

For example, while or after selecting the network device group, the NaaSdevice may obtain the information about the network device group. Thatis, the candidate device group obtained by the NaaS device is a setdenoted by information about a device, so that while obtaining thenetwork device group, the NaaS device obtains the information about thenetwork device group. The information about the network device groupincludes: an identifier of each device in the network device group andan attribute of each device in the network device group. For example,the identifier of the device may be information that can be used toidentify the device, such as an address of the device, a number of thedevice, a name of the device, or an identity of the device; theattribute of the device may be an interface of the device, and theinterface may be denoted by “interface”. Alternatively, according to aneed of an actual application, the information about the network devicegroup may further include information, such as a layer 2 network (L2network) or a subnet, that can be used to locate each device in thenetwork device group, and may be not specifically limited in thisembodiment of the present application.

For example, the identifier information is used to identify the firstdevice group. The NaaS device may locally save in advance a candidatedevice group corresponding to the first device group, or locally saves acandidate device group corresponding to the identifier information. TheNaaS device may obtain, in a local reading manner according to theidentifier information, the candidate device group corresponding to theidentifier information. Alternatively, the NaaS device may obtain acandidate device group corresponding to the identifier information fromoutside according to the identifier information. If the identifierinformation further includes a Controller identifier (ID), the NaaSdevice may communicate with a Controller corresponding to the ControllerID, and obtain a candidate device group corresponding to the ControllerID from the Controller corresponding to the Controller ID.Alternatively, the NaaS device saves a correspondence between theController ID and a candidate device group. The NaaS device receives aController ID that is input by a user, and obtain a correspondingcandidate device group according to the Controller ID that is input bythe user. In this embodiment of the present application, a manner inwhich the NaaS device obtains a candidate device group may be notspecifically limited.

For example, the NaaS device may obtain a network resource model of adevice included in a candidate device group. The network resource modelof the device included in the candidate device group may denote acapability of the device. The network resource model of the device mayinclude: an identifier of the device and an attribute of the device. Thenetwork resource model may further include: a network hierarchy to whichthe device belongs, where the network hierarchy may be a layer 2, alayer 3, or another layer, the layer 2 may be a data link layer in anopen systems interconnection (OSI) model, the layer 3 may be a networklayer in the OSI model, and the another layer may be a layer such as atransmission layer in the OSI model. The network resource model mayfurther include: a function of the device, where the function of thedevice may be a filtering function, a multicast function, or the like.

For example, the method by using which the NaaS device selects a networkdevice group from a candidate device group may include: if the candidatedevice group includes multiple devices that meet the condition,selecting any one of the devices as a device in the network devicegroup, or selecting a device having the smallest device number or adevice having the largest device number as a device in the networkdevice group.

Optionally, when the candidate device group in this embodiment of thepresent application includes multiple devices that meet the condition,the NaaS device may select a network device group according to a networkhierarchy to which a device belongs. For example, the NaaS devicedetermines whether network hierarchies of the multiple devices that meetthe condition are the same. If the network hierarchies are different,the NaaS device selects, from the multiple devices that meet thecondition, a device having the lowest network hierarchy as a device inthe network device group, which helps to reduce a requirement of aservice on a network resource. If the network hierarchies are the same,the NaaS device may randomly select one device as a device in thenetwork device group. Alternatively, when the network hierarchies arethe same, the NaaS device may select a device having the smallest devicenumber or a device having the largest device number as a device in thenetwork device group.

Optionally, when the candidate device group includes multiple devicesthat are in a same network hierarchy or when multiple devices exist inthe lowest network hierarchy, the NaaS device in this embodiment of thepresent application may further send IDs of the multiple devices to aController, obtain, from the Controller, load statuses of the devices,for example, quantities of loads that the devices carry and CPUutilization of the devices. The NaaS device may select the networkdevice group according to a load balancing technology and the loadstatuses of the devices.

Optionally, the NaaS device in this embodiment of the presentapplication may receive a load status, obtained by the Controller inreal time, of a device, or receive a load status, obtained by theController within a preset time period, of a device, which may be notspecifically limited in this embodiment of the present application.

103: The NaaS device obtains a first forwarding rule according to thecondition, where the first forwarding rule corresponds to the networkdevice group.

For example, the NaaS device may convert the condition into a forwardingrule of a device in the network device group. The device in the networkdevice group may provide, for a user according to the forwarding rule, aservice meeting a communication requirement of the user. In thisembodiment of the present application, the first forwarding rule may beembodied as a parameter group shown in FIG. 2, where the parameter groupincludes a rule and an action, and the parameter group may be denoted as(rule, action).

For example, the NaaS device may first obtain the information about thenetwork device group, and then obtain the first forwarding rule; or theNaaS device may first obtain the first forwarding rule, and then obtainthe information about the network device group; or the NaaS device mayperform the foregoing two operations at the same time, which may be notspecifically limited in this embodiment of the present application.

104: The NaaS device sends the first forwarding rule and the informationabout the network device group to a controller.

For example, the NaaS device may communicate with the Controller byusing a protocol, such as an OpenFlow protocol, that is supported byboth the NaaS device and the Controller, or the NaaS device maycommunicate with the Controller by using another protocol, and detailsare not described herein example by example.

Optionally, before the NaaS device sends the first forwarding rule andthe information about the network device group to the controller, theNaaS device may select a Controller. An example in which the Controllermanages a device in a physical network is used, and the NaaS device mayselect a Controller in the following three manners:

If one Controller exists in the physical network, and the Controller isconfigured to manage devices in the physical network, the NaaS devicemay send the first forwarding rule and the information about the networkdevice group to the Controller, and the Controller delivers the firstforwarding rule to the network device group.

If at least two Controllers, such as a first Controller and a secondController, exist in the physical network, and the first Controller andthe second Controller manage devices in different areas in the physicalnetwork, the information about the network device group may furtherinclude a Controller ID. The NaaS device may find, according to theController ID, a Controller that manages the network device group. TheNaaS device sends the first forwarding rule and the information aboutthe network device group to the Controller corresponding to theController ID, and the Controller corresponding to the Controller IDdelivers the first forwarding rule to the network device group.

If at least three Controllers, such as a third Controller, a fourthController, and a fifth Controller, exist in the physical network, thethird Controller manages devices in an area in the physical network, thefourth Controller manages devices in another area in the physicalnetwork, the areas managed by the third Controller and the fourthController are not completely the same, and the fifth Controller maymanage the third Controller and the fourth Controller, the NaaS devicemay send the first forwarding rule and the information about the networkdevice group to the fifth Controller, and the fifth Controller maydeliver the first forwarding rule to the network device group; or thefifth Controller searches for a Controller, for example, the fourthController, that manages the network device group, and forwards thefirst forwarding rule and the information about the network device groupto the fourth Controller, and the fourth Controller may deliver thefirst forwarding rule to the network device group.

For example, if the information, obtained by the NaaS device, about thenetwork device group corresponds to a physical network device, theController may determine, according to the information, sent by the NaaSdevice, about the network device group, one or more devices in physicalnetwork devices that are managed by the controller. If the information,obtained by the NaaS device, about the network device group correspondsto a virtual network device, the Controller needs to first performvirtual-physical mapping, to obtain a physical network devicecorresponding to the virtual network device.

In this embodiment of the present application, a manner in which theController manages devices in a network, a process in which theController performs virtual-physical mapping, and the like may be notspecifically limited, as long as the NaaS device can send, to acorresponding network device by using the Controller, the firstforwarding rule and the information about the network device group thatare obtained according to the contract.

In this embodiment of the present application, a user needs to provide,for an NaaS device, only a contract or a parameter that reflects acommunication requirement of the user, and the NaaS device may obtainidentifier information and a condition in the contract, and obtaininformation about a network device group according to the identifierinformation and the condition. The NaaS device may deliver a firstforwarding rule that is obtained according to the condition, toconfigure a service on a selected network device group, which helps tosimplify operations and improve configuration efficiency. In addition,the NaaS device may further select the network device group according toa cost of a device, a load status of a device, and the like, which helpsto reduce a cost of a device and improve running efficiency of aservice.

Optionally, after 103, the method provided in this embodiment of thepresent application may further include: performing, by the NaaS device,a rule check on the first forwarding rule. The rule check may be a rulecheck of the network device group, or a rule check between the networkdevice group and another device in a candidate device group. When therule check is the rule check of the network device group, if the firstforwarding rule passes the rule check, the NaaS device sends the firstforwarding rule and the information about the network device group tothe Controller. If the first forwarding rule does not pass the rulecheck, the NaaS device may calibrate the first forwarding rule, and sendthe information about the network device group and a calibrated firstforwarding rule to the Controller. When the rule check is the rule checkbetween the network device group and the another device in the candidatedevice group, if the first forwarding rule passes the rule check, theNaaS device sends the first forwarding rule and the information aboutthe network device group to the Controller. If the first forwarding ruledoes not pass the rule check, the NaaS device may calibrate the firstforwarding rule, and send the information about the network device groupand a calibrated first forwarding rule to the Controller, or the NaaSdevice calibrates a rule of the another device in the candidate devicegroup, and sends the information about the network device group and thefirst forwarding rule to the Controller.

Optionally, after 103, the method provided in this embodiment of thepresent application may further include: obtaining, by the NaaS device,a detection packet according to the first forwarding rule and theinformation about the network device group, where the detection packetis used to obtain a detection result from the network device group, andthe detection result is a result of communication that is performed bythe network device group according to the first forwarding rule; andsending, by the NaaS device, the detection packet to the controller. Thecontroller sends the detection packet to the network device groupaccording to the information, included in the detection packet, aboutthe network device group.

Optionally, after the sending, by the NaaS device, the detection packetto the controller, the method further includes: receiving, by the NaaSdevice, the detection result sent by the controller; and if thedetection result meets a preset condition, adjusting, by the NaaSdevice, the contract according to the detection result. For example, theNaaS device may determine, by means of comparison, whether the detectionresult meets the preset condition.

The access contract, the routing contract, and the multicast contractdescribed above are separately used as examples to explain and describea service configuration process in the embodiments of the presentapplication below.

Embodiment 1

Embodiment 1 is an embodiment related to an access contract. Anapplication scenario of Embodiment 1 may be a scenario of a data center.Devices of the data center may be divided into the following USGsaccording to communication capabilities of the devices: a public networkUSG, a private network USG, a network (Web) USG, an application (App)USG, a database (DB) USG, and the like. In Embodiment 1, an accessfiltering service during access of the public network USG to the Web USGis used as an example for description.

1. A User Determines a Public Network USG and a Web USG According to aCommunication Requirement.

The user may obtain an access condition for a terminal to access a Webserver, and determine one or more terminals that need to access the Webserver as one USG, to form the public network USG.

The user determines the Web USG according to a Web server included in adata center network that is used. In this example, the Web USG is afirst identifier. For example, a device group identified by the Web USGmay be a set of devices included in an area A in FIG. 3, that is, thedevice group identified by the Web USG includes the Web server. Thedevice group identified by the Web USG may be further a set of devicesincluded in an area B in FIG. 3, that is, the device group identified bythe Web USG includes the Web server and an access router 1.Alternatively, the device group identified by the Web USG may be furthera set of devices included in the data center network. In this embodimentof the present application, specific composition of the device groupidentified by the Web USG may be not specifically limited. In thisembodiment of the present application, the device group identified bythe Web USG includes at least the Web server.

2. An NaaS Device Obtains an Access Contract.

For example, the NaaS device may receive an access contract that isinput by a user in a manner of a command line, a Web interface, or thelike. Alternatively, the NaaS device may further predefine descriptionmodels of some access contracts, and the NaaS device may generate anaccess contract according to a parameter that is input by the user and apredefined description model. In this embodiment of the presentapplication, a specific manner in which the NaaS device obtains anaccess contract may be not specifically limited.

For example, in the embodiment corresponding to FIG. 3, the accesscontract may be denoted as <USG2, access contract>, the USG2 may includean ID of a Web USG. The USG2 may further include an ID of a deviceincluded in a device group identified by the Web USG. Optionally, theUSG2 may further include an ID of a Controller corresponding to a deviceincluded in the Web USG. The ID of the device included in the devicegroup identified by the Web USG may be Web1 and Web2 in FIG. 3. Theaccess contract is a communication requirement for accessing the devicegroup identified by the Web USG, and may include a rule and an action,where the rule may include a port whose number is 22 and a protocolbeing the Secure Shell (SSH), and the action may include permittingaccess.

3. The NaaS Device Obtains Information about a Network Device Group.

For example, that the NaaS device obtains information about a networkdevice group may include: The NaaS device obtains a second device groupcorresponding to a Web USG; the NaaS device may select a first devicefrom the second device group according to a condition; and the NaaSdevice obtains information about the first device. Alternatively, thatthe NaaS device obtains information about a network device group mayinclude: The NaaS device reads a locally saved second device group; theNaaS device may traverse the second device group, and select, from thesecond device group, a first device that meets a Web USG and acondition; and the NaaS device obtains information about the firstdevice. The second device group belongs to a candidate device group, andthe first device belongs to the network device group.

For example, the NaaS device may obtain the second device groupaccording to the Web USG. The second device group may be a set ofdevices included in an area C in FIG. 3, a set of devices included in anarea D in FIG. 3, or a set of devices included in the data centernetwork. In this embodiment of the present application, composition ofthe second device group may be not specifically limited, and the seconddevice group includes at least a device that can implement a filteringfunction.

An example in which the area C or the area D in FIG. 3 is separatelyused as the second device group is used below to explain and describe aprocess in which the NaaS device obtains information about a networkdevice group in this embodiment of the present application.

If the second device group is a set of devices included in the area C,that is, the area C includes two egress routers, which are respectivelyR1 and R2, that the NaaS device obtains information about a networkdevice group may include:

(1) Devices that meet the condition of the access contract are obtained.

For example, the condition included in the access contract in thisembodiment is an access condition for a public network USG to access aWeb USG, that is, the network device group needs to have a filteringfunction. The NaaS device may learn functions of the devices included inthe area C, and determine that both R1 and R2 have a filtering function.

(2) The first device is selected from the devices that meet thecondition of the access contract, and the information about the firstdevice is obtained.

For example, the NaaS device selects either of R1 and R2 as the firstdevice.

Optionally, the NaaS device may select a device having a relatively lownetwork hierarchy as the first device, that is, perform selectionaccording to network hierarchies to which R1 and R2 belong. If both R1and R2 are layer 3 devices, the NaaS device may select either of R1 andR2 as the first device. If R1 is a layer 3 device and R2 is a layer 4device, the NaaS device may select R1 as the first device, which helpsto reduce a requirement of a service on a network resource.

Optionally, the NaaS device may further perform selection according toquantities of loads carried by R1 and R2. If a quantity of loads carriedby R2 is less than a quantity of loads carried by R1, the NaaS devicemay select R2 as the first device. When R1 and R2 are in a same networkhierarchy, the NaaS device may further perform selection according tothe quantities of loads carried by R1 and R2. That is, when both R1 andR2 are layer 3 devices, and the quantity of loads carried by R2 isrelatively small, the NaaS device may select R2 as the first device,which helps to improve running efficiency of a service.

Optionally, after determining that R1 and R2 have a filtering function,or after learning that network hierarchies of R1 and R2 are the same,the NaaS device may select an egress router having a relatively smallnumber or a relatively large number as the first device.

For example, the NaaS device may obtain an identifier and an interfaceof the selected first device, for example, obtain a node ID and aninterface of the first device. The NaaS device may use the obtainedidentifier and interface as the information about the first device.

If the second device group is a set of devices included in the area D,that is, the area D includes two egress routers such as R1 and R2, twofirewall devices such as FW1 and FW2, and two aggregation routers suchas R3 and R4, that the NaaS device obtains information about a networkdevice group may include:

(1) Devices having a filtering function are selected according to thecondition included in the access contract.

For example, among the devices included in the area D, neither R3 nor R4has a filtering function, and the NaaS device selects R1, R2, FW1, andFW2 from the area D.

(2) The first device is selected from R1, R2, FW1, and FW2, and theinformation about the first device is obtained.

For example, the NaaS device may select, from R1, R2, FW1, and FW2, adevice having a relatively low network hierarchy. If a network hierarchyis a layer 3 for R1 and R2, and is a layer 4 for FW1 and FW2, the NaaSdevice may select R1 and R2. The NaaS device may select either devicefrom R1 and R2 as the first device, or the NaaS device may select, fromR1 and R2, a device having a relatively small quantity of loads as thefirst device.

Optionally, after determining that R1, R2, FW1, and FW2 have a filteringfunction, or after learning that R1 and R2 are in a same networkhierarchy, the NaaS device may select a device having a relatively smallnumber or a relatively large number as the first device.

For example, the NaaS device may obtain an identifier and an interfaceof the selected first device, and use the identifier and the interfaceas the information about the first device.

Optionally, before the devices having a filtering function are selected,that the NaaS device obtains information about a network device groupmay further include: determining whether network devices connected toWeb1 or Web2 exist in the second device group. If the network devicesconnected to Web 1 or Web2 do not exist, the NaaS device traverses thesecond device group according to the method in (1), and selects deviceshaving a filtering function. If the network devices connected to Web1 orWeb2 exist, the NaaS device may obtain, from the network devicesconnected to Web1 or Web2, devices having a filtering function, whichhelps to narrow down a search range.

4. The NaaS Device Obtains a First Forwarding Rule.

For example, that the NaaS device obtains a first forwarding rule mayinclude: The NaaS device obtains a first match field and a first actionfrom the condition of the access contract, where the first match fieldcorresponds to the communication requirement for accessing the devicegroup identified by the first identifier, and the first actioncorresponds to an access operation; and the NaaS device generates aforwarding rule of the first device according to the first match fieldand the first action. The forwarding rule of the first device is thefirst forwarding rule.

For example, the first match field corresponds to the condition in theaccess contract, and may include at least one of a port, a protocol, anIP address, or a MAC address. For example, the port whose number is 22,and the protocol is the SSH. The first action corresponds to an accessoperation, and may include at least one of permitting access, forbiddingaccess, redirection, or mirroring.

In this embodiment of the present application, the forwarding rule ofthe first device may be an access control list (ACL), and the ACL may beobtained after the NaaS device converts the condition in the accesscontract. For example, if the rule in the access contract may include aport whose number is 22 and a protocol being the SSH protocol, and theaction in the access contract may include permitting access, the ACLobtained by the NaaS device may be denoted as: rule permit protocol SSHdport 22, where dport 22 denotes that a destination port whose number is22.

5. The NaaS Device Delivers the First Forwarding Rule and theInformation about the Network Device Group to a Controller.

For example, if the information about the selected first device includesR1 and an interface1, and the ACL is rule permit protocol SSH dport 22,(node, interface, rule, action) delivered by the NaaS device to theController may be denoted as (R1, interface1, rule permit protocol SSHdport 22), where the interface 1 may be used to identify an interface ofR1, and dport 22 may be a destination port carried in a packet receivedby R1.

Optionally, after obtaining the forwarding rule of the first device, theNaaS device may further perform a rule check on the obtained forwardingrule of the first device. For example, in this embodiment of the presentapplication, the rule check may be performed on the forwarding rule ofthe first device in the following two implementation manners.

In a first implementation manner, the rule check is performed on theforwarding rule of the first device. Performing the rule check on theforwarding rule of the first device may be performing the rule check onthe first device or performing the rule check between the first deviceand another device in the second device group.

(1) The performing the rule check on the first device includes:

The NaaS device performs a conflict check on the forwarding rule of thefirst device and a second forwarding rule, where the second forwardingrule is a forwarding rule that is already configured on the firstdevice. If a conflict exists, that is, the forwarding rule of the firstdevice does not pass the rule check, the NaaS device obtains acalibrated forwarding rule of the first device, and sends the calibratedforwarding rule of the first device and the information about the firstdevice to the Controller. If a conflict does not exist, that is, theforwarding rule of the first device passes the rule check, the NaaSdevice sends the forwarding rule of the first device and the informationabout the first device to the Controller.

For example, for an access service of a research and developmentdepartment, the following already configured forwarding rule is set on adevice S0: a research and development department server cannot access anexternal network, and all employees of the research and developmentdepartment may access an internal network of a company by using a deviceS1. Meanwhile, for a pre-research group that belongs to the research anddevelopment department, during automatic configuration of the accessservice, the network device group selected by the NaaS device is thedevice S0, and the obtained first forwarding rule is: a pre-researchgroup server cannot access an SSH service, and a pre-research groupemployee may access an external network by using a device S2. In such acase, the NaaS device may perform a rule check on the first forwardingrule by using the following method.

(a) For the forwarding rule “a research and development departmentserver cannot access an external network, and all employees of theresearch and development department may access an internal network of acompany by using a device S1” that is already configured on the deviceS0, an IP address of an employee of the research and developmentdepartment is located in a network segment 10.0.0.0/8, that is, anetwork segment 10.0.0.1 to 10.255.255.255, where “\” denotes“excluding”, an IP address of the research and development departmentserver is 10.0.0.1, Y denotes “or”, a port 80 is used to access anexternal network, and ->{S1} denotes “by using the device S1”. Thealready configured forwarding rule may be described as:SrcAddr:10.0.0.0/8\(SrcAddr:10.0.0.1 Y DstPort:80)->{S1}. The NaaSdevice may decompose the already configured forwarding rule to obtainthree first rules:

(a1) The research and development department server having the IPaddress of 10.0.0.1 cannot access the external network by using thedevice S1.

A first rule A1: SrcAddr:10.0.0.1:{ }, where when content in { } isempty, it denotes discarding. In this embodiment of the presentapplication, discarding means skipping execution of all actions in thealready configured forwarding rule. For example, an action in thealready configured forwarding rule is “go to the device S1”, and theaction of discarding in the first rule A1 is “not go to the device S1”.

(a2) An employee of the research and development department cannotaccess the external network by using the device S1.

A first rule A2: DstPort: 80: { }.

(a3) An employee of the research and development department accesses theinternal network by using the device S1.

A first rule A3: SrcAddr:10.0.0.0/8: {S1}, where {S1} denotes “go to thedevice S1”.

(b) For the first forwarding rule “a pre-research group server cannotaccess an SSH service, and a pre-research group employee may access anexternal network by using a device S2”, an IP address of a pre-researchgroup employee is located in a network segment 10.2.0.0/16, that is, thenetwork segment 10.2.0.1 to 10.2.255.255, “\” denotes “excluding”, an IPaddress of the pre-research group server is 10.2.0.1, Y denotes “or”, aport 22 is used to access the SSH service, and ->{S2} denotes “by usingthe device S2”. In this way, the first forwarding rule may be describedas: SrcAddr: 10.2.0.0/16\(SrcAddr: 10.2.0.1 Y DstPort:22)->{S2}. TheNaaS device may decompose the first forwarding rule to obtain threesecond rules:

(b1) The pre-research group server having the IP address of 10.2.0.1cannot access the SSH service by using the device S2.

A second rule B1: SrcAddr:10.2.0.1:{ }, where when content in { } isempty, it denotes discarding.

(b2) A pre-research employee cannot access the SSH service by using thedevice S2. A second rule B2: DstPort:22:{ }.

(b3) A pre-research employee accesses the external network by using thedevice S2.

A second rule B3: SrcAddr:10.2.0.0/16:{S2}.

It may be understood that, as may be learned from the description of thealready configured forwarding rule, priorities of the first rules areA1>A2>A3 in a descending order. As may be learned from the descriptionof the first forwarding rule, priorities of the second rules areB1>B2>B3 in a descending order.

Optionally, to achieve an effect of complete coverage, one matching rulehaving the lowest priority may be added to both the first rules and thesecond rules, where a match field of the matching rule is a wildcardcharacter, and an action is discarding. For example, a first matchingrule is newly added as a first rule A4: *: { }, and the first rule A4may be denoted as: discarding any packet that does not match matchfields in the first rules A1, A2, and A3. A second matching rule isnewly added as a second rule B4: *: II, and the second rule B4 may bedenoted as: discarding any packet that does not match match fields inthe second rules B1, B2, and B3.

(c) The NaaS device performs negation on a first rule to obtain a firstnegation rule. Performing negation on the first rule is keeping a matchfield of the first rule unchanged and performing negation on an actionof the first rule.

A first negation rule C1: SrcAddr:10.0.0.1: {S1}, where {S1} denotes “goto the device S1”.

A first negation rule C2: DstPort:80: {S1}.

A first negation rule C3: SrcAddr:10.0.0.0/8: {S1 }, where {S1 } denotes“not go to the device S1”.

A first negation rule C4: *: {S1}.

(d) The NaaS device performs negation on a second rule to obtain asecond negation rule. Performing negation on the second rule is keepinga match field of the second rule unchanged and performing negation on anaction of the second rule.

A second negation rule D1: SrcAddr:10.2.0.1: {S2}, where {S2} denotes“go to the device S2”.

A second negation rule D2: DstPort:22: {S2}.

A second negation rule D3: SrcAddr:10.2.0.0/16:{S1 }, where {S2 }denotes “not go to the device S2”.

A second negation rule D4: *: {S2}.

A priority of each first negation rule is the same as a priority of acorresponding first rule, and a priority of each second negation rule isthe same as a priority of a corresponding second rule.

(e) The NaaS device combines the first negation rules and the secondnegation rules two by two according to a rule synthesis principle, togenerate 16 first execution rules.

(e1) A priority of a first execution rule is sorted according topriorities of synthesizing two negation rules of the first executionrule. For example, if a priority of the already configured forwardingrule is higher than that of the first forwarding rule, the NaaS devicemay perform sorting according to priorities of first negation rulesobtained by decomposing the already configured forwarding rule. When thefirst negation rules have a same priority, the NaaS device may performsorting according to priorities of second negation rules obtained bydecomposing the first forwarding rule. For example, the first executionrules obtained by the NaaS device are C1D1, C1D2, C2D1, C3D2, C3D4, andC4D1, and therefore, the first execution rules may be sorted asC1D1>C1D2>C2D1>C3D2>C3D4>C4D1 according to priorities in a descendingorder.

(e2) The NaaS device may use each first negation rule as one element,and perform arrangement according to a priority order of the firstnegation rules, to form a first matrix P1, where the first matrix P1 isa column matrix. The NaaS device uses each second negation rule as oneelement, and performs arrangement according to a priority order of thesecond negation rules, to form a second matrix P2, where the secondmatrix P2 is a row matrix. For example, a matrix formed by rules havinghigh priorities may be used as a column matrix.

(e3) The NaaS device performs multiplication processing on the firstmatrix and the second matrix, to obtain a first execution rule matrix.

${\overset{\_}{P\; 1} \times \overset{\_}{P\; 2}} = {{\begin{bmatrix}{C\; 1} \\{C2} \\{C3} \\{C4}\end{bmatrix} \times \left\lbrack {{D1},\ {D2},\ {D3},\ {D4}} \right\rbrack} = \begin{bmatrix}{{C\; 1\; D\; 1},{C\; 2D\; 1},{C\; 3D\; 1},{C\; 4D\; 1}} \\{{C\; 1D\; 2},{C\; 2D\; 2},{C\; 3D\; 2},{C\; 4D\; 2}} \\{{C\; 1\; D\; 3},{C\; 2D\; 3},{C\; 3D\; 3},{C\; 4D\; 3}} \\{{C\; 1D\; 4},{C\; 2D\; 4},{C\; 3D\; 4},{C\; 4D\; 4}}\end{bmatrix}}$

(e4) After obtaining the first execution rule matrix by means ofcalculation, the NaaS device may obtain a first execution rule accordingto the rule synthesis principle.

The rule synthesis principle may include: If a match field of a firstnegation rule and a match field of a second negation rule are of a sametype, continue to determine whether an intersection set exists betweenthe match field of the first negation rule and the match field of thesecond negation rule. If no intersection set exists between the matchfield of the first negation rule and the match field of the secondnegation rule, a rule obtained by synthesizing the first negation ruleand the second negation rule is an invalid rule. If an intersection setexists between the match field of the first negation rule and the matchfield of the second negation rule, the intersection set between thematch field of the first negation rule and the match field of the secondnegation rule and an intersection set between an action of the firstnegation rule and an action of the second negation rule form a validfirst execution rule. If a match field of a first negation rule and amatch field of a second negation rule are of different types, a unionset between the match field of the first negation rule and the matchfield of the second negation rule and an intersection set between anaction of the first negation rule and an action of the second negationrule form a valid first execution rule. Optionally, in anotherapplication embodiment, the rule synthesis principle may furtherinclude: If there is no intersection set after negation is performed onthe intersection set between the action of the first negation rule andthe action of the second negation rule, a rule obtained by synthesizingthe first negation rule and the second negation rule is also consideredas an invalid rule.

For C1D1, the first negation rule C1 is: SrcAddr:10.0.0.1:{S1}, and thesecond negation rule D1 is: SrcAddr:10.2.0.1:{S2}. A match field of C1is an IP address 10.0.0.1, a match field of D1 is an IP address10.2.0.1, and the two match fields are of a same type, but have nointersection set. Therefore, C1D1 is an invalid rule.

For C1D2, the first negation rule C1 is: SrcAddr:10.0.0.1:{S1}, and thesecond negation rule D2 is: DstPort:22:{S2}. A match field of C1 is anIP address 10.0.0.1, a match field of D2 is a port address 22, and thetwo match fields are of different types. Therefore, C1D2 uses a unionset between the match field of C1 and the match field of D2 and anintersection set between an action of C1 and an action of D2, and C1D2is 10.0.0.1,22:{S1I S2}.

For C1D3, the first negation rule C1 is: SrcAddr; 10.0.0.1; {S1}, andthe second negation rule D3 is: SrcAddr; 10.2.0.0/16; {S2 }. A matchfield of C1 is an IP address 10.0.0.1, a match field of D3 is10.2.0.0/16, that is, 10.2.0.1 to 10.2.255.255, and the two match fieldsare of a same type, but have no intersection set. Therefore, C1D3 is aninvalid rule.

For C1D4, the first negation rule C1 is: SrcAddr; 10.0.0.1; {S1}, andthe second negation rule D4 is: *; {S2}. A match field of C1 is an IPaddress 10.0.0.1, a match field of D4 is a wildcard character *, and thetwo match fields are of a same type. Therefore, C1D4 uses anintersection set between the match field of C1 and the match field of D4and an intersection set between an action of C1 and an action of D4, andC1D4 is 10.0.0.1:{S1I S2}.

For C2D1, the first negation rule C2 is: DstPort:80:{S1}, and the secondnegation rule D1 is: SrcAddr:10.2.0.1:{S2}. A match field of C2 is aport address 80, a match field of D1 is an IP address 10.2.0.1, and thetwo match fields are of different types. Therefore, C2D1 uses a unionset between the match field of C2 and the match field of D1 and anintersection set between an action of C2 and an action of D1, and C2D1is 10.2.0.1,80:{S1I S2}.

For C2D2, the first negation rule C2 is: DstPort:80:{S1}, and the secondnegation rule D2 is: DstPort:22:{S2}. A match field of C2 is a portaddress 80, a match field of D2 is a port address 22, and the two matchfields are of a same type, but have no intersection set. Therefore, C2D2is an invalid rule.

For C2D3, the first negation rule C2 is: DstPort:80:{S1}, and the secondnegation rule D3 is: SrcAddr:10.2.0.0/16:{S2 }. A match field of C2 is aport address 80, a match field of D3 is 10.2.0.0/16, that is, 10.2.0.1to 10.2.255.255, and the two match fields are of a same type. Therefore,C2D3 uses a union set between the match field of C2 and the match fieldof D3 and an intersection set between an action of C2 and an action ofD3, and C2D3 is 10.2.0.0/16, 80:{S1I S2 }.

For C2D4, the first negation rule C2 is: DstPort:80:{S1}, and the secondnegation rule D4 is: *:{S2}. A match field of C2 is a port address 80, amatch field of D4 is a wildcard character *, and the two match fieldsare of a same type. Therefore, C2D4 uses an intersection set between thematch field of C2 and the match field of D4 and an intersection setbetween an action of C2 and a action of D4, and C2D4 is 80:{S1I S2}.

For C3D1, the first negation rule C3 is: SrcAddr:10.0.0.0/8:{S1 }, andthe second negation rule D1 is: SrcAddr:10.2.0.1:{S2}. A match field ofC3 is a network segment address 10.0.0.0/8, that is, 10.0.0.0 to10.255.255.255, a match field of D1 is an IP address 10.2.0.1, and thetwo match fields are of a same type, and have an intersection set.Therefore, C3D1 uses the intersection set between the match field of C3and the match field of D1 and an intersection set between an action ofC3 and the action of D1, and C3D1 is 10.2.0.1:{S1 I S2}.

For C3D2, the first negation rule C3 is: SrcAddr:10.0.0.0/8:{S1 }, andthe second negation rule D2 is: DstPort:22:{S2}. A match field of C3 isa network segment address 10.0.0.0/8, that is, 10.0.0.0 to10.255.255.255, a match field of D2 is a port address 22, and the twomatch fields are of different types. Therefore, C3D2 uses a union setbetween the match field of C3 and the match field of D2 and anintersection set between an action of C3 and an action of D2, and C3D2is 10.0.0.0/8,22:{S1 I S2}.

For C3D3, the first negation rule C3 is: SrcAddr; 10.0.0.0/8:{S1 }, andthe second negation rule D3 is: SrcAddr; 10.2.0.0/16:{S2 }. A matchfield of C3 is a network segment address 10.0.0.0/8, that is, 10.0.0.0to 10.255.255.255, a match field of D3 is 10.2.0.0/16, that is, 10.2.0.1to 10.2.255.255, and the two match fields are of a same type, and havean intersection set. Therefore, C3D3 uses the intersection set betweenthe match field of C3 and the match field of D3 and an intersection setbetween an action of C3 and an action of D3, and C3D3 is 10.2.0.0/16:{S1I S2 }.

For C3D4, the first negation rule C3 is: SrcAddr:10.0.0.0/8:{S1 }, andthe second negation rule D4 is: *:{S2}. A match field of C3 is a networksegment address 10.0.0.0/8, that is, 10.0.0.0 to 10.255.255.255, a matchfield of D4 is a wildcard character *, and the two match fields are of asame type. Therefore, C3D4 uses an intersection set between the matchfield of C3 and the match field of D4 and an intersection set between anaction of C3 and an action of D4, and C3D4 is 10.0.0.0/8:{S1 I S2}.

For C4D1, the first negation rule C4 is: *: {S1}, and the secondnegation rule D1 is: SrcAddr:10.2.0.1:{S2}. A match field of C4 is awildcard character *, a match field of D1 is an IP address 10.2.0.1, andthe two match fields are of a same type, and have an intersection set.Therefore, C4D1 uses the intersection set between the match field of C4and the match field of D1 and an intersection set between an action ofC4 and an action of D1, and C4D1 is 10.2.0.1:{S1I S2}.

For C4D2, the first negation rule C4 is: *: {S1}, and the secondnegation rule D2 is: DstPort:22:{S2}. A match field of C4 is a wildcardcharacter *, a match field of D2 is a port address 22, and the two matchfields are of a same type. Therefore, C4D2 uses an intersection setbetween the match field of C4 and the match field of D2 and anintersection set between an action of C4 and an action of D2, and C4D2is 22:{S1I S2}.

For C4D3, the first negation rule C4 is: *: {S1}, and the secondnegation rule D3 is: SrcAddr:10.2.0.0/16:{S2 }. A match field of C4 is awildcard character *, a match field of D3 is 10.2.0.0/16, that is,10.2.0.1 to 10.2.255.255, and the two match fields are of a same type.Therefore, C4D3 uses an intersection set between the match field of C4and the match field of D3 and an intersection set between an action ofC4 and an action of D3, and C4D3 is 10.2.0.0/16:{S1I S2 }.

For C4D4, the first negation rule C4 is: *: {S1}, and the secondnegation rule D4 is: *:{S2}. A match field of C4 is a wildcard character*, a match field of D4 is a wildcard character *, and the two matchfields are of a same type. Therefore, C4D4 uses an intersection setbetween the match field of C4 and the match field of D4 and anintersection set between an action of C4 and an action of D4, and C4D4is *: {S1I S2}.

(f) The NaaS device deletes an invalid rule, uses a remaining firstexecution rule as a valid first execution rule, performs negation oneach valid first execution rule, and then performs conversion accordingto a protocol supported by the device S0 to obtain a forwarding entrycorresponding to the device S0.

For example, performing negation on a valid first execution rule iskeeping a match field unchanged and performing negation on an action.

For example, S1I S2 =S1 YS2 ={ }, S1I S2 =S1 YS2=S2 , S1I S2 =S1YS2 =S1,and S1I S2 =S1YS2=S2, S2 .

In the first execution rule matrix formed in (e):

Because C1D1 is an invalid rule, C1D1 is deleted, and negation does notneed to be performed on C1D1.

Negation is performed on C1D2 (10.0.0.1,22:{S1I S2}), to obtain10.0.0.1,22:{S1I S2 }, where S1I S2 ={ } Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.0.0.1,22:{ }.

Because C1D3 is an invalid rule, C1D3 is deleted, and negation does notneed to be performed on C1D3.

Negation is performed on C1D4 (10.0.0.1:{S1I S2}), to obtain10.0.0.1:{S1I S2 }, where S1I S2 ={ }. Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.0.0.1:{ }.

Negation is performed on C2D1 (10.2.0.1,80:{S1I S2}), to obtain10.2.0.1,80:{S1I S2 }, where S1I S2 ={ }. Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.2.0.1,80:{ }.

Because C2D2 is an invalid rule, C2D2 is deleted, and negation does notneed to be performed on C2D2.

Negation is performed on C2D3 (10.2.0.0/16.80; {S1I S2 }), to obtain10.2.0.0/16,80; {S1I S2 }, where S1I S2 =S2 . Therefore, the negation ofthe first execution rule may be simplified and denoted as 10.2.0.0/16,80:{S2}.

Negation is performed on C2D4 (80:{S1I S2}), to obtain 80:{S1I S2 }where S1I S2 ={ } Therefore, the negation of the first execution rulemay be simplified and denoted as 80:{ }.

Negation is performed on C3D1 (10.2.0.1:{S1 I S2}), to obtain10.2.0.1:{S1I S2 }, where S1I S2 =S1. Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.2.0.1:{S1}.

Negation is performed on C3D2 (10.0.0.0/8,22:{S1 I S2}), to obtain10.0.0.0/8,22:{S1I S2 }, where S1I S2 =S1. Therefore, the negation ofthe first execution rule may be simplified and denoted as10.0.0.0/8,22:{S1}.

Negation is performed on C3D3 (10.2.0.0/16:{S1 I S2 }), to obtain10.2.0.0/16:{S1I S2 }, where S1I S2 =S2, S2 . Therefore, the negation ofthe first execution rule may be simplified and denoted as10.2.0.0/16:{S1, S2}.

Negation is performed on C3D4 (10.0.0.0/8:{S1 I S2}), to obtain10.0.0.0/8:{S1I S2 }, where S1I S2 =S1. Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.0.0.0/8: {S1}.

Negation is performed on C4D1 (10.2.0.1:{S1I S2}), to obtain 10.2.0.1:{S1I S2 }, where S1I S2 ={ }. Therefore, the negation of the firstexecution rule may be simplified and denoted as 10.2.0.1:{ }.

Negation is performed on C4D2 (22:{S1I S2}), to obtain 22:{S1I S2 },where S1I S2 ={ }. Therefore, the negation of the first execution rulemay be simplified and denoted as 22:{ }.

Negation is performed on C4D3 (10.2.0.0/16:{S1I S2 }), to obtain10.2.0.0/16:{S1I S2 }, where S1I S2 =S2 . Therefore, the negation of thefirst execution rule may be simplified and denoted as 10.2.0.0/16:{S2}.

Negation is performed on C4D4 (*:{S1I S2}), to obtain *:{S1I S2 }, whereS1I S2 ={ }. Therefore, the negation of the first execution rule may besimplified and denoted as *:{ }.

After performing negation on valid first execution rules, the NaaSdevice performs conversion according to a protocol supported by thedevice S0 to obtain corresponding forwarding entries, to enable thedevice S0 to forward a packet according to the forwarding entry.Optionally, priorities of the forwarding entries may have a same orderas the priorities of the first execution rules corresponding to theforwarding entries. After receiving a packet, the device S0 may forwardthe packet to another forwarding device according to a forwarding entryhaving the highest priority in forwarding entries that match the packet,for example, forward the packet to the device S1 or the device S2. Inthis way, invalid rules in which a conflict exists are deleted, whichmay avoid a rule conflict between an already configured forwarding ruleand the first forwarding rule, so that the device S0 can execute boththe already configured forwarding rule and the first forwarding rule.

(2) The performing the rule check between the first device and anotherdevice in the second device group includes:

The NaaS device determines whether the forwarding rule of the firstdevice and a forwarding rule of a second device in the second devicegroup form a transmission abnormality. If a transmission abnormality isformed, the NaaS device obtains a third forwarding rule, and the NaaSdevice sends the forwarding rule of the first device and the informationabout the first device to the Controller. If no transmission abnormalityis formed, the NaaS device sends the forwarding rule of the first deviceand the information about the first device to the Controller. Forexample, the third forwarding rule may be a calibrated forwarding ruleof the second device. For example, the NaaS device may calibrate theforwarding rule of the second device, to obtain a calibrated forwardingrule of the second device. The second device may directly communicatewith the first device, or the second device may indirectly communicatewith the first device.

The rule check is used to detect whether a transmission abnormalityoccurs in the second device group. If a transmission abnormality exists,it indicates that a packet cannot be correctly forwarded to adestination node, and rule calibration needs to be performed. Thetransmission abnormality may be a loop or a blackhole, or may be anothertransmission abnormality, and details are not described one by one.During the rule check, the NaaS device may perform at least one type ofdetection of loop detection or blackhole detection.

If the second device group is a set of devices included in the area D inFIG. 3, the loop detection and the blackhole detection are separatelyused as examples to explain and describe a process of checking theforwarding rule of the first device below.

Example Regarding the Loop Detection

For example, egress routers in the area D are R1 and R2, and aggregationrouters are R3 and R4. In the area D, an interface 1 of R1 is connectedto R3, an interface 2 of R3 is connected to an access router 1, and theaccess router 1 may communicate with a Web server. The NaaS device maylearn forwarding rules configured on all devices included in the area D.The forwarding rule configured on R1 is: forwarding a packet by using anoutbound interface 1. The forwarding rule configured on R3 is:forwarding a packet by using an outbound interface 2. The packet is apacket obtained after R1 performs filtering according to the forwardingrule of the first device. Based on the forwarding rules configured on R1and R2, with reference to the network shown in FIG. 3, after R1 obtainsthe packet according to the forwarding rule of the first device, thepacket may pass through the interface 1 of R1 and the interface 2 of R3,and reach the access router 1. No transmission abnormality occurs in thesecond device group, that is, the packet may be correctly sent to theaccess router 1 connected to the Web server, and the forwarding rule ofthe first device passes the rule check.

In the area D, the interface 1 of R1 is connected to R3, the interface 3of R3 is connected to R4, and the interface 2 of R4 is connected to R1.The forwarding rule configured on R1 is: forwarding a packet by usingthe interface 1. The forwarding rule configured on R3 is: forwarding apacket by using the interface 3. The forwarding rule configured on R4is: forwarding a packet by using the interface 2. The packet is a packetobtained after R1 performs filtering according to the forwarding rule ofthe first device. Based on the forwarding rules that are alreadyconfigured on R1, R3, and R4, with reference to the network shown inFIG. 3, after R1 obtains the packet according to the forwarding rule ofthe first device, the packet may pass through the interface 1 of R1 andthe interface 3 of R3, and reach R4. R4 sends, to R1 by using theinterface 2 of R4, the packet from R3. R4 may cause a loop to form inthe area D, and the packet cannot reach the access router 1 connected tothe Web server, that is, the forwarding rule of the first device doesnot pass the rule check. The NaaS device may calibrate the forwardingrule configured on R4, for example, calibrate the forwarding ruleconfigured on R4 to be sending the packet by using the interface 3.

Example Regarding the Blackhole Detection

When a transmission abnormality such as a loop and a blackhole occurs,eventually a packet cannot be correctly forwarded to the destinationnode. A difference lies in that: When a loop occurs, a packet isforwarded continuously and circularly; and when a blackhole occurs, apacket cannot be forwarded to another node.

For example, egress routers in the area D are R1 and R2, and aggregationrouters are R3 and R4. In the area D, the interface 1 of R1 is connectedto R3, the interface 3 of R3 is connected to R4, and the interface 2 ofR4 is connected to R1. The forwarding rule configured on R1 is:forwarding a packet by using the interface 1. The forwarding ruleconfigured on R3 is: forwarding a packet by using the interface 3. Noforwarding rule is configured on R4. The packet is a packet obtainedafter R1 performs filtering according to the forwarding rule of thefirst device. Based on the forwarding rules that are already configuredon R1 and R3, with reference to the network shown in FIG. 3, after R1obtains the packet according to the forwarding rule of the first device,the packet may pass through the interface 1 of R1 and the interface 3 ofR3, and reach R4. Because no forwarding rule is configured on R4, R4cannot correctly forward the packet to the access router 1. R4 causes ablackhole to form in the area D, that is, the forwarding rule of thefirst device does not pass the rule check. The NaaS device needs tocalibrate a forwarding rule of R4, for example, the NaaS device mayconfigure, on R4, a forwarding rule of forwarding a packet by using theinterface 3.

Optionally, another device, for example, R3, in the second device groupmay also cause a transmission abnormality, and details are not describedherein example by example.

Optionally, in this embodiment of the present application, transmissionabnormality detection may be performed on all devices in the seconddevice group, or may be performed on some designated devices in thesecond device group, or may be performed on a device, on which aforwarding rule is being configured currently, in the second devicegroup, which may be not specifically limited in this embodiment of thepresent application. For the device on which a forwarding rule is beingconfigured currently, at least two following cases may be understood:

Case 1: A condition in an access contract includes at least two accesscommunication requirements. For example, a first access communicationrequirement includes: a first rule and a first action, where the firstrule includes a port whose number is 22 and the SSH protocol, and thefirst action is permitting access; and a second access communicationrequirement includes: a second rule and a second action, where thesecond rule includes a port being 80 and the Hypertext Transfer Protocol(HTTP), and the second action is permitting access. The NaaS device mayseparately obtain, for each access communication requirement accordingto the method in 101 to 104 in this embodiment of the presentapplication, a first forwarding rule and information about a networkdevice group that are corresponding to the communication requirement.

Case 2: The NaaS device currently receives access contracts that areinput by at least two users, for example, an access contract 1 that isinput by a user 1, where a condition in the access contract 1 includes:a first rule and a first action, where the first rule includes a portwhose number is 22 and the SSH protocol, and the first action ispermitting access; and an access contract 2 that is input by a user 2,where a condition in the access contract 2 includes: a second rule and asecond action, where the second rule includes a port being 80 and theHTTP protocol, and the second action is permitting access. The NaaSdevice may obtain, according to the method in 101 to 104 in thisembodiment of the present application, a first forwarding rule andinformation about a network device group that are corresponding to thecontract 1, and a first forwarding rule and information about a networkdevice group that are corresponding to the contract 2.

Optionally, to implement correct configuration of a service, the NaaSdevice may further perform duplicate name detection on a contract thatis input by a user, to prevent different users from defining contractsby using a same name.

In a second implementation manner, an actual test is performed onservice running of a device in a physical network by using theforwarding rule of the first device, to discover a service abnormalityor perform fault location.

In an example, in this embodiment of the present application, an actualtest may be at least be embodied as at least one of the following threeaspects: rule validity, connectivity, or quality of service (QoS).

(1) Rule Validity

For example, after obtaining the forwarding rule of the first device andthe information about first device, the NaaS device may send theforwarding rule of the first device and the information about firstdevice to the Controller. The Controller may deliver the forwarding ruleof the first device to the first device. After sending the forwardingrule of the first device and the information about first device to theController, the NaaS device may further perform an actual test on astatus of configuring the forwarding rule of the first device by thefirst device, to ensure that the first device correctly configures theforwarding rule of the first device, that is, the forwarding rule of thefirst device already takes effect on the first device.

For example, after receiving the forwarding rule, delivered by theController, of the first device, the first device records aconfiguration status of the forwarding rule of the first device. TheNaaS device may perform rule validity detection in the following manner:The NaaS device constructs a first detection packet, and sends the firstdetection packet to the first device. For example, the NaaS device maydeliver the first detection packet to the first device by using theController. The first detection packet is used to request the firstdevice to report the configuration status of the forwarding rule of thefirst device. The configuration status may be already taking effect ornot taking effect. After receiving the first detection packet, the firstdevice obtains the configuration status of the forwarding rule of thefirst device according to the first detection packet. The first devicemay obtain a first detection result packet according to theconfiguration status. The first device sends the first detection resultpacket to the NaaS device. For example, the first device sends the firstdetection result packet to the NaaS device by using the Controller.

(2) Connectivity

The NaaS device may further perform connectivity detection in the datacenter network shown in FIG. 3, and perform fault location on a devicein the network. In an example, in this embodiment of the presentapplication, the connectivity detection may be embodied as loopdetection and/or blackhole detection.

Specifically, the NaaS device may calculate reachable address space anda path set by using a head space analysis (HSA) technology, and performloop detection and/or blackhole detection based on the reachable addressspace and the path set. In this embodiment, the NaaS device performsloop detection and/or blackhole detection on the data center network.For the loop detection, the loop detection method in the rule checkprocess may be used, and details are not described herein. For theblackhole detection, the blackhole detection method in the rule checkprocess may be used, and details are not described herein. Optionally,if the NaaS device learns that a loop exists in the data center network,the NaaS device may further construct a second detection packet, anddeliver the second detection packet to a path on which the loop exists.If the NaaS device learns that a blackhole exists in the data centernetwork, the NaaS device may further construct a third detection packet,and deliver the third detection packet to a path on which the blackholeexists. The NaaS device may deliver the second detection packet or thethird detection packet by using the Controller, and confirm, in a mannerof an actual test, whether a loop and/or a blackhole exist/exists in anetwork.

(3) QoS

The NaaS device may further perform QoS detection on communicationbetween any two devices in the network in the data center network shownin FIG. 3. In an example, in this embodiment of the present application,the QoS detection may include at least one of a bandwidth, a delay,jitter, or a packet loss rate.

Delay detection is used as an example to explain and describe a QoSdetection process in this embodiment of the present application below.

The NaaS device constructs a fourth detection packet used to detect adelay from R1 to the access router 1, and forwards the fourth detectionpacket to R1 by using the Controller. Correspondingly, R1 receives thefourth detection packet sent by the Controller, and sends the fourthdetection packet to the access router 1. The fourth detection packetsent by R1 to the access router 1 may include a sending timestamprecorded by R1. After receiving the fourth detection packet, the accessrouter 1 may further record a receiving timestamp, and the access router1 calculates a delay according to the sending timestamp and thereceiving timestamp. The access router 1 obtains a fourth detectionresult packet. The fourth detection result packet includes the delay,and the access router 1 sends the fourth detection result packet to theNaaS device by using the Controller.

For detection of a parameter such as a bandwidth, jitter, or a packetloss rate, refer to the delay detection method. A correspondingdetection packet is generated, and a detection result is obtained byusing the corresponding detection packet. Details are not describedherein example by example.

In addition, for the second implementation manner, this embodiment ofthe present application may be further described as follows: Afterobtaining a detection result, the NaaS device may directly feed back thedetection result to a user. For example, that the forwarding rule of thefirst device already takes effect, which device causes a blackhole, orQoS between any two devices in the network is fed back to the user. Theuser performs subsequent processing according to the detection result.Alternatively, the NaaS device may further perform associated processingon an access contract according to the detection result and a presetcondition. A process of the associated processing is explained anddescribed below.

(a) For the rule validity detection, the preset condition may be thatthe forwarding rule of the first device does not take effect. If thefirst detection result packet received by the NaaS device denotes thatthe forwarding rule of the first device does not take effect, the NaaSdevice may determine that a detection result meets the preset condition,and needs to perform associated processing on the access contract. Forexample, the NaaS device may generate a parameter group<event,condition, action> according to the detection result and the presetcondition, and adjust the access contract by using the parameter group.The event denotes an event on which associated processing is performed,and may be rule validity in this example. The condition denotes acondition of associated processing, that is, the preset condition, andin this example, may be that the forwarding rule of the first devicedoes not take effect. The action denotes an action of associatedprocessing, and in this example, may be: reselecting the informationabout the network device group, for example, selecting R2 in FIG. 3 asthe first device, and sending the forwarding rule of the first deviceand information about R2 to the Controller; or sending the forwardingrule of the first device and the information about first device to theController again. For example, in the foregoing example, the firstdevice is R1 in FIG. 3, and the forwarding rule of the first device andthe information about R1 are sent to the Controller.

(b) For the connectivity detection, an example in which loop detectionis performed by using the second detection packet is used. The presetcondition may be that a loop occurs. If a second detection result packetreceived by the NaaS device denotes that a loop exists in the network,the NaaS device may determine that a detection result meets the presetcondition, and needs to perform associated processing on the accesscontract. For example, the NaaS device may generate a parametergroup<event, condition, action> according to the detection result andthe preset condition, and adjust the access contract by using theparameter group. The event denotes an event on which associatedprocessing is performed, and may be a loop in this example. Thecondition denotes a condition of associated processing, that is, thepreset condition, and in this example, may be that a loop exists. Theaction denotes an action of associated processing, and in this example,may be modifying a forwarding rule of a device in which a loop occurs,for example, modifying the forwarding rule of R4 in the network shown inFIG. 3.

It should be noted that, a process of associated processing of ablackhole is similar to a process of associated processing of a loop,and details are not described herein. For a parameter group generatedfor a blackhole, an event may be a blackhole, a condition may be that ablackhole exists, and an action may be configuring a forwarding rule ona device in which the blackhole occurs.

(c) For the QoS detection, an example in which the delay detection isperformed by using the fourth detection packet is used. The presetcondition may be that a delay value is greater than a preset delayvalue. If the fourth detection result packet received by the NaaS devicedenotes that a delay value in an actual test is greater than the presetdelay value, the NaaS device may determine that a detection result meetsthe preset condition, and needs to perform associated processing on theaccess contract. For example, the NaaS device may generate a parametergroup<event, condition, action> according to the detection result andthe preset condition, and adjust the access contract by using theparameter group. The event denotes an event on which associatedprocessing is performed, and may be a delay in this example. Thecondition denotes a condition of associated processing, that is, thepreset condition, and in this example, may be that a delay value isgreater than the preset delay value. The action denotes an action ofassociated processing, and in this example, may be adjusting the presetdelay value to a delay value in an actual test.

It should be noted that, a method of associated processing of aparameter such as a bandwidth, jitter, or a packet loss rate is similarto a method of associated processing of a delay, and details are notdescribed herein. In a parameter group generated for a packet loss rate,an event may be a packet loss rate, a condition may be that a packetloos rate is greater than a preset packet loss rate, and an action maybe adjusting the preset packet loss rate to a packet loss rate in anactual test. In a group parameter generated for jitter, an event may bejitter, a condition may be that a jitter value is greater than a presetjitter value, and an action may be adjusting the preset jitter value toa jitter value in an actual test. In a parameter group generated forbandwidth, an event may be bandwidth, a condition may be that abandwidth a less than a preset bandwidth, and an action may be adjustingthe preset bandwidth to a bandwidth in an actual test.

In addition, it should be noted that, the NaaS device may adjust theaccess contract when a detection result meets a requirement of thepreset condition, so as to implement associated processing.Alternatively, the NaaS device may display a detection result to a userfor viewing, and adjust the access contract only after receiving anindication from the user. Alternatively, the NaaS device mayautomatically adjust the access contract according to an indication whena detection result meets the preset condition, where the indication isset by a user and is used to perform associated processing. In anexample, the user may set, when inputting the access contract in theNaaS device, an indication used to perform associated processing. Forexample, the indication used to perform associated processing is acoordination parameter. Specifically, when a value of the coordinationparameter is Y, it denotes that associated processing needs to beperformed, and when a value of the coordination parameter is N, itdenotes that associated processing does not need to be performed.Alternatively, when the access contract includes the coordinationparameter, it denotes that associated processing needs to be performed,and when the access contract does not include the coordinationparameter, it denotes that associated processing does not need to beperformed. In this embodiment of the present application, a conditionfor an NaaS device to perform associated processing, a manner in which auser sets an indication used to perform associated processing, and thelike may be not specifically limited.

Embodiment 2

Embodiment 2 is an embodiment related to a routing contract. Anapplication scenario of Embodiment 2 may be an interconnection scenarioin a data center. Devices in the interconnection scenario in the datacenter may be divided into the following USGs according to communicationcapabilities of the devices: a site USG, a public cloud USG, and thelike. As shown in FIG. 4, a site 1 USG, a site 2 USG, and a site 3 USGmay communicate with each other two by two, and the site 3 USG maycommunicate with a public cloud USG. In Embodiment 2, an example ofimplementing a requirement on communication between the site 1 USG andthe site 2 USG is used for description. The communication requirement inin this example may be a transmission requirement of a path.

1. A user determines the site 1 USG and the site 2 USG according to acommunication requirement.

For example, the user may determine the site 1 USG and the site 2 USG inthis example with reference to the data center shown in FIG. 3. As shownin FIG. 4, the user defines some or all devices included in a datacenter 1 as the site 1 USG, and in this example, the site 1 USG may be asecond identifier; the user defines some or all devices included in adata center 2 as the site 2 USG, and in this example, the site 2 USG maybe a third identifier. FIG. 4 does not completely show networkarchitectures of the data centers 1 and 2, and for the rest part, referto FIG. 3.

2. An NaaS device obtains a routing contract.

For example, in the embodiment corresponding to FIG. 4, the routingcontract may be denoted as <USG3, USG4, routing contract>. The USG3 mayinclude an ID of the site 1 USG. The USG3 may further include an ID of adevice included in a device group identified by the site 1 USG.Optionally, the USG3 may further include an ID of a Controllercorresponding to the device group identified by the site 1 USG. The USG4may include an ID of the site 2 USG and an ID of a device included in adevice group identified by the site 2 USG. Optionally, the USG4 mayfurther include an ID of a Controller corresponding to a device includedin the site 2 USG. The routing contract is a requirement oncommunication between the device group identified by the site 1 USG andthe device group identified by the site 2 USG, and may include a ruleand an action, where the rule may include a bandwidth being 10 G and adelay being 10 ms, and the action may include setting QoS.

For example, the NaaS device may receive a routing contract that isinput by a user in a manner of a command line, a Web interface, or thelike. Alternatively, the NaaS device may further predefine descriptionmodels of some routing contracts, and the NaaS device may automaticallygenerate a routing contract according to a parameter that is input bythe user and a predefined description model. In this embodiment of thepresent application, a specific manner in which the NaaS device obtainsa routing contract may be not specifically limited.

For example, “us” in a command line that is input by the user may be anabbreviation of “user”. The NaaS device may obtain the routing contractby using the following command lines that are input by the user:

(1) Create Classifier

neutron classifier-create Routing-Control—ingress site1USG—egresssite2USG

(2) Create Routing Contract using the Classifier

neutron contract-create Routing-Control-Contract—classifierRouting-Control—action QoS—bandwidth 10G—delay 10 ms—coordination Y

(3) Create USG providing the Contract

neutron usg-create site1 USG—consumes-contract Routing-Control-Contract

(4) Create User in site1 USG

neutron us-create—usg site1USG

(5) Create USG providing the Contract

neutron usg-create site2USG—consumes-contract Routing-Control-Contract

(6) Create User in site2USG

neutron us-create—usg site2USG

3. The NaaS device obtains information about a network device group.

For example, that the NaaS device obtains information about a networkdevice group may include: The NaaS device obtains a third device groupcorresponding to the site 1 USG, where the third device group includes adevice used as a source node, the NaaS device selects a third devicefrom the third device group according to the condition, where the thirddevice is the source node, and the NaaS device obtains information aboutthe third device; and the NaaS device obtains a fourth device groupcorresponding to the site 2 USG, where the fourth device group includesa device used as a destination node, the NaaS device selects a fourthdevice from the fourth device group according to the condition, wherethe fourth device is the destination node, and the NaaS device obtainsinformation about the fourth device. For example, the source node inthis example may be a source node of a path between the third devicegroup and the fourth device group, and the destination node may be adestination node of the path; or the source node in this example may bea node that sends a packet, and the destination node may be a node thatreceives the packet.

Alternatively, that the NaaS device obtains information about a networkdevice group may include: The NaaS device reads a locally saved thirddevice group, the NaaS device may traverse the third device group, andselect, from the third device group, a third device that meets the site1 USG and the condition, and the NaaS device obtains information aboutthe third device; and the NaaS device reads a locally saved fourthdevice group, the NaaS device may traverse the fourth device group, andselect, from the fourth device group, a fourth device that meets thesite 2 USG and the condition, and the NaaS device obtains informationabout the fourth device.

In this example, the third device group and the fourth device groupbelong to a candidate device group, and the third device and the fourthdevice belong to the network device group.

For example, the NaaS device may obtain the third device group accordingto the site 1 USG, and obtain the fourth device group according to thesite 2 USG. In this embodiment of the present application, compositionof the third device group and the fourth device group may be notspecifically limited, the third device group includes at least a devicethat can communicate with a device outside the data center 1, and thefourth device group includes at least a device that can communicate witha device outside the data center 2. For a manner in which the NaaSdevice obtains the third device group and the fourth device group, referto the implementation manner for obtaining a second device group inEmbodiment 1, and details are not described herein.

After obtaining the third device group, the NaaS device may select thethird device from the third device group according to the condition. Fora manner in which the NaaS device selects the third device, refer to theimplementation manner for selecting a first device in Embodiment 1, anddetails are not described herein. For example, the NaaS device mayobtain an identifier of the selected third device and an interface ofthe third device, and use the obtained identifier and interface as theinformation about the third device.

After obtaining the fourth device group, the NaaS device may select thefourth device from the fourth device group according to the condition.For a manner in which the NaaS device selects the fourth device, referto the implementation manner for selecting a first device in Embodiment1, and details are not described herein. For example, the NaaS devicemay obtain an identifier of the selected fourth device and an interfaceof the fourth device, and use the obtained identifier and interface asthe information about the fourth device.

4. The NaaS device obtains a first forwarding rule.

For example, the NaaS device obtains a second match field and a secondaction from the condition of the routing contract, where the secondmatch field corresponds to the requirement on communication between thedevice group identified by the second identifier and the device groupidentified by the third identifier, and the second action corresponds tocommunication between the device group identified by the secondidentifier and the device group identified by the third identifier; andthe NaaS device generates a forwarding rule of the third device and aforwarding rule of the fourth device according to the second match fieldand the second action. The first forwarding rule includes the forwardingrule of the third device and the forwarding rule of the fourth device.

For example, the second match field corresponds to the condition in therouting contract, and may include at least one of QoS, a virtual privatenetwork (VPN) label, or a committed access rate (CAR). For example, abandwidth is 10 M, and the bandwidth belongs to QoS. The second actioncorresponds to the communication operation, and may include at least oneof setting QoS or setting a VPN.

For example, if the condition in the routing contract is a bandwidthrequirement between the third device group and the fourth device group,the forwarding rule of the third device and the forwarding rule of thefourth device may be denoted as: enabling an MPLS-TE configuration, thatis, mpls te bandwidth max-reservable-bandwidth 100000000. Optionally, ifthe information about the selected third device includes R11 and aninterface 1, the forwarding rule of the third device may be furtherdenoted as: enabling an MPLS-TE configuration, and enabling a bandwidthconstraint configuration on the interface1, that is, mpls te bandwidthmax-reservable-bandwidth 100000000. If the information about theselected fourth device includes R22 and the interface1, the forwardingrule of the fourth device may be further denoted as: enabling an MPLS-TEconfiguration, and enabling a bandwidth constraint configuration on theinterface1, that is, mpls te bandwidth max-reservable-bandwidth100000000.

5. The NaaS device delivers the first forwarding rule and theinformation about the network device group to a Controller.

In this example, a parameter group (node, interface, rule, action)delivered by the NaaS device to the Controller may be denoted as (R11;interface1; enable an MPLS-TE configuration, mpls te bandwidthmax-reservable-bandwidth 100000000; set QoS) and (R22; interface1;enable an MPLS-TE configuration, mpls te bandwidthmax-reservable-bandwidth 100000000; set QoS).

Optionally, after receiving the first forwarding rule and theinformation about the network device group that are sent by the NaaSdevice, the Controller may obtain a path between a source node R11 and adestination node R22, and perform bandwidth constraint configuration onnodes on the path according to a bandwidth requirement. For example, thepath further includes forwarding nodes R3 and R4, and the Controller mayseparately perform bandwidth constraint configuration on R11, R22, R3,and R4.

Optionally, this embodiment of the present application further providestwo implementation manners of a rule check, which are described below byusing examples.

In a first implementation manner, a rule check is performed on the firstforwarding rule. The performing a rule check on the first forwardingrule may be performing a rule check on the network device group, orperforming a rule check between the network device group and anotherdevice in the candidate device group.

(1) The performing a rule check on the network device group includes:

(a) The NaaS device performs a conflict check on the forwarding rule ofthe third device and a fourth forwarding rule, where the fourthforwarding rule is a forwarding rule that is already configured on thethird device. If a conflict exists, that is, the forwarding rule of thethird device does not pass the rule check, the NaaS device calibratesthe forwarding rule of the third device, and obtains a calibratedforwarding rule of the third device. The first forwarding rule includesthe forwarding rule of the fourth device and the calibrated forwardingrule of the third device.

(b) The NaaS device performs a conflict check on the forwarding rule ofthe fourth device and a fifth forwarding rule, where the fifthforwarding rule is a forwarding rule that is already configured on thefourth device. If a conflict exists, that is, the forwarding rule of thefourth device does not pass the rule check, the NaaS device calibratesthe forwarding rule of the fourth device, and obtains a calibratedforwarding rule of the fourth device. The first forwarding rule includesthe forwarding rule of the third device and the calibrated forwardingrule of the fourth device.

(c) The NaaS device performs a rule check on the forwarding rule of thethird device according to the method shown in (a), and further performsa rule check on the forwarding rule of the fourth device according tothe method shown in (b). If neither the forwarding rule of the thirddevice nor the forwarding rule of the fourth device passes the rulecheck, the NaaS device calibrates the forwarding rule of the thirddevice and the forwarding rule of the fourth device. The firstforwarding rule may include a calibrated forwarding rule of the thirddevice and a calibrated forwarding rule of the fourth device.

For example, a rule conflict in this example may be: For the thirddevice R11, if the fourth forwarding rule is that a packet is forwardedto a router R3 via an interface2, the forwarding rule of the thirddevice is that a packet is forwarded to the router R3 via theinterface1. In an application process, a case in which another ruleconflict occurs may also exist, and details are not described hereinexample by example. For a method by using which the NaaS device resolvesa rule conflict, refer to the method used above when a forwarding ruleof the first device conflicts with the second forwarding rule, anddetails are not described herein.

(2) The performing a rule check between the network device group andanother device in the candidate device group includes:

(a) The NaaS device determines whether the forwarding rule of the thirddevice and a forwarding rule of a fifth device in the third device groupform a transmission abnormality. If a transmission abnormality isformed, the NaaS device obtains a sixth forwarding rule, and the NaaSdevice sends the forwarding rule of the third device and the informationabout the third device to the Controller. If no transmission abnormalityis formed, the NaaS device sends the forwarding rule of the third deviceand the information about the third device to the Controller. Forexample, the sixth forwarding rule may be a forwarding rule obtainedafter the NaaS device calibrates the forwarding rule of the fifthdevice. The fifth device may directly communicate with the third device,or the fifth device may indirectly communicate with the third device.

(b) The NaaS device determines whether the forwarding rule of the fourthdevice and a forwarding rule of a sixth device in the fourth devicegroup form a transmission abnormality. If a transmission abnormality isformed, the NaaS device obtains a seventh forwarding rule, and the NaaSdevice sends the forwarding rule of the fourth device and theinformation about the fourth device to the Controller. If notransmission abnormality is formed, the NaaS device sends the forwardingrule of the fourth device and the information about the fourth device tothe Controller. For example, the seventh forwarding rule may be aforwarding rule obtained after the NaaS device calibrates the forwardingrule of the sixth device. The sixth device may directly communicate withthe fourth device, or the sixth device may indirectly communicate withthe fourth device.

(c) The NaaS device performs a rule check in the third device groupaccording to the method shown in (a), and further performs a rule checkin the fourth device group according to the method shown in (b). If atransmission abnormality exists in both the third device group and thefourth device group, the NaaS device obtains the sixth forwarding ruleand the seventh forwarding rule separately.

For example, the transmission abnormality may be a case such as a loopor a blackhole because of which a packet cannot be correctly forwardedto a destination node. For a manner for detecting a transmissionabnormality, refer to the foregoing process of performing loop detectionand blackhole detection in the second device group, and details are notdescribed herein.

In a second implementation manner, an actual test is performed onservice running of a device in a physical network by using the firstforwarding rule, to discover a service abnormality or perform faultlocation.

In an example, in this embodiment of the present application, an actualtest may be at least embodied as at least one of the following threeaspects: rule validity, connectivity, or QoS.

(1) Rule Validity

(a) The NaaS device constructs a fifth detection packet, and deliversthe fifth detection packet to the third device by using the Controller,where the fifth detection packet is used to request the third device toreport a configuration status of the forwarding rule of the thirddevice, and the configuration status may be already taking effect or nottaking effect. After receiving the fifth detection packet, the thirddevice obtains the configuration status of the forwarding rule of thethird device according to the fifth detection packet. The third devicemay obtain a fifth detection result packet according to theconfiguration status, and send the fifth detection result packet to theNaaS device by using the Controller.

(b) The NaaS device constructs a sixth detection packet, and deliversthe sixth detection packet to the fourth device by using the Controller,where the sixth detection packet is used to request the fourth device toreport a configuration status of the forwarding rule of the fourthdevice, and the configuration status may be already taking effect or nottaking effect. After receiving the sixth detection packet, the fourthdevice obtains the configuration status of the forwarding rule of thefourth device according to the sixth detection packet. The fourth devicemay obtain a sixth detection result packet according to theconfiguration status, and send the sixth detection result packet to theNaaS device by using the Controller.

(c) The NaaS device performs validity detection on the forwarding ruleof the third device according to the method shown in (a), and furtherperforms validity detection on the forwarding rule of the fourth deviceaccording to the method shown in (b).

(2) Connectivity

The NaaS device may further perform connectivity detection in thenetwork shown in FIG. 4, and perform fault location on a device in thenetwork. In an example, in this embodiment of the present application,the connectivity detection may be loop detection and/or blackholedetection. For a connectivity detection method in this example, refer tothe method used when connectivity detection is performed in the datacenter network shown in FIG. 3 in Embodiment 1, and details are notdescribed herein. In this example, the NaaS device may performconnectivity detection on at least one network of the data center 1, thedata center 2, or the Internet.

(2) QoS

The NaaS device may further perform QoS detection between any twodevices of an egress router R11, an egress router R22, and a device inthe Internet in the network shown in FIG. 4. In an example, in thisembodiment of the present application, the QoS detection may include atleast one of a bandwidth, a delay, jitter, or a packet loss rate. For aQoS detection method in this example, refer to the method used when QoSdetection is performed in the data center network shown in FIG. 3 inEmbodiment 1, and details are not described herein.

Optionally, after obtaining a detection result, the NaaS device mayfurther perform associated processing on the routing contract by usingthe detection result and a preset condition. For a method by using whichthe NaaS device performs associated processing on the routing contract,refer to the implementation manner of associated processing inEmbodiment 1, and details are not described herein.

Embodiment 3

Embodiment 3 is another embodiment related to a routing contract. Anapplication scenario of Embodiment 3 may be a scenario of a broadbandintelligent service. Devices in a network of the broadband intelligentservice may be divided into the following USGs according tocommunication capabilities of the devices: a user group USG, a publicnetwork USG, and the like. As shown in FIG. 5, a user group 1 USG maycommunicate with a public network USG, and a user group 2 USG maycommunicate with the public network USG. In Embodiment 3, an example ofimplementing communication between the user group 1 USG and the usergroup 2 USG is used for description. In this example, a communicationrequirement may be creating a VPN.

1. An NaaS device obtains a routing contract.

For example, in the embodiment corresponding to FIG. 5, the routingcontract may be denoted as <USG3, USG4, routing contract>. The USG3 mayinclude an ID of the user group 1 USG. The USG3 may further include anID of a device included in a device group identified by the user group 1USG. Optionally, the USG3 may further include an ID of a Controllercorresponding to a device included in the user group 1 USG. The USG4 mayinclude an ID of the user group 2 USG. The USG4 may further include anID of a device included in a device group identified by the user group 2USG. Optionally, the USG4 may further include an ID of a Controllercorresponding to a device included in the user group 2 USG. The routingcontract may include a rule and an action, where the rule may include aVPN label being 100, and the action may include setting a VPN.

For example, the NaaS device may receive a routing contract that isinput by a user in a manner of a command line, a Web interface, or thelike. Alternatively, the NaaS device may further predefine descriptionmodels of some routing contracts, and the NaaS device may automaticallygenerate a routing contract according to a parameter that is input bythe user and a predefined description model. In this embodiment of thepresent application, a specific manner in which the NaaS device obtainsa routing contract may be not specifically limited.

For example, “us” in a command line that is input by the user may be anabbreviation of “user”. The NaaS device may obtain the routing contractby using the following command lines that are input by the user:

(1) Create Classifier

neutron classifier-create VPN-Control—ingress user group 1 USG—egressuser group 2 USG

(2) Create Routing Contract using the Classifier

neutron contract—create VPN—Control-Contract—classifierVPN—Control—action MARK—vpnlable 100

(3) Create USG providing the Contract

neutron usg-create user group 1 USG—consumes-contractVPN-Control-Contract

(4) Create User in user group 1 USG

neutron us-create—usg user group 1 USG

(5) Create USG providing the Contract

neutron usg-create user group 2 USG—consumes-contractVPN-Control-Contract

(6) Create User in user group 2 USG

neutron us-create—usg user group 2 USG

2. The NaaS device obtains information about a network device group.

For example, that the NaaS device obtains information about a networkdevice group may include: The NaaS device obtains a candidate devicegroup according to the user group 1 USG and the user group 2 USG in therouting contract; the NaaS device selects the network device group fromthe candidate device group according to a condition in the routingcontract; and the NaaS device obtains the information about the networkdevice group.

For a manner in which the NaaS device obtains the candidate devicegroup, refer to the implementation manner for obtaining a third devicegroup and a fourth device group in Embodiment 2, and details are notdescribed herein. For a manner in which the NaaS device selects thenetwork device group, refer to the implementation manner for selecting athird device and a fourth device in Embodiment 2, and details are notdescribed herein. For a manner in which the NaaS device obtains theinformation about the network device group, refer to the implementationmanner for obtaining information about the third device and informationabout the fourth device in Embodiment 2, and details are not describedherein.

For example, the information (node, interface) of the selected networkdevice group may be denoted as: (R1, interface1) and (R2, interface1).

3. The NaaS device obtains a first forwarding rule.

In this embodiment of the present application, the first forwarding rulemay be obtained after the condition in the routing contract isconverted.

For example, the first forwarding rule may be denoted as a VPNconfiguration. The first forwarding rule may include a forwarding rulefor R1 and a forwarding rule for R2. The forwarding rule for R1 may be:enabling a VPN global configuration, that is, mpls static-l2vcdestination user group 2 USG transmit-vpn-label 100 receive-vpn-label100; and the forwarding rule for R2 may be: enabling a VPN globalconfiguration, that is, mpls static-l2vc destination user group 1 USGtransmit-vpn-label 100 receive-vpn-label 100. Optionally, the forwardingrule for R1 may be further denoted as enabling a VPN globalconfiguration, and enabling a VPN label on the interface 1, that is,mpls static-l2vc destination user group 2 USG transmit-vpn-label 100receive-vpn-label 100; and the forwarding rule for R2 may be denoted as:enabling a VPN global configuration, and enabling a VPN label on theinterface 1, that is, mpls static-l2vc destination user group 1 USGtransmit-vpn-label 100 receive-vpn-label 100.

4. The NaaS device delivers the first forwarding rule and theinformation about the network device group to a Controller.

In this example, (node, interface, rule, action) delivered by the NaaSdevice to the Controller may be denoted as (R1; interface1; enable VPNglobal configuration, mpls static-l2 vc destination user group 2 USGtransmit-vpn-label 100 receive-vpn-label 100; set VPN) and (R2;interface1; enable VPN global configuration, mpls static-l2vcdestination user group 2 USG transmit-vpn-label 100 receive-vpn-label100; set VPN).

Optionally, after obtaining the first forwarding rule, the NaaS devicemay further perform a rule check on the obtained first forwarding rule.For example, in this embodiment of the present application, a rule checkmay be performed on the first forwarding rule in two implementationmanners. In a first implementation manner, the NaaS device performs arule check on the first forwarding rule; and in a second implementationmanner, the NaaS device performs an actual test on service running of adevice in a physical network by using the first forwarding rule. For arule check method, refer to the implementation manners of a rule checkin Embodiment 1 and Embodiment 2, and details are not described herein.

Embodiment 4

Embodiment 4 is an embodiment related to a multicast contract. Anapplication scenario of Embodiment 4 may be a scenario of an enterprisenetwork. Devices in the enterprise network may be divided into thefollowing USGs according to network segments: a subnet USG, a multicastUSG, and the like. For example, network segments may be divided in amanner of a department, an office area, or the like. As shown in FIG. 6,a subnet 1 USG may communicate with a multicast USG, and a subnet 2 USGmay communicate with the multicast USG. In Embodiment 4, an example ofimplementing a communication requirement for the subnet 1 USG to jointhe multicast USG is used for description. In this example, the subnet 1USG may be a fourth identifier, and the multicast USG may be a fifthidentifier.

1. An NaaS device obtains a multicast contract.

For example, in the embodiment corresponding to FIG. 6, the multicastcontract may be denoted as <USG5, USG multicast, multicast contract>.The USG5 may include an ID of the subnet 1 USG. The USG5 furtherincludes an ID of a device included in a device group identified by thesubnet 1 USG. Optionally, the USG5 may further include an ID of aController corresponding to a device included in the subnet 1 USG. TheUSG multicast is used to identify a multicast group, for example,identify a multicast group whose address is 225.1.1.1. The multicastcontract is a communication requirement for the subnet 1 USG to join amulticast group, and may include a rule and an action, where the rulemay include an address of a multicast group being 225.1.1.1, and theaction may include joining a multicast group.

For example, the NaaS device may receive a multicast contract that isinput by a user in a manner of a command line, a Web interface, or thelike. Alternatively, the NaaS device may further predefine descriptionmodels of some multicast contracts, and the NaaS device mayautomatically generate a multicast contract according to a parameterthat is input by the user and a predefined description model. In thisembodiment of the present application, a specific manner in which theNaaS device obtains a multicast contract may be not specificallylimited.

For example, “us” in a command line that is input by the user may be anabbreviation of “user”. The NaaS device may obtain the multicastcontract by using the following command lines that are input by theuser:

(1) Create Classifier

neutron classifier-create Multicast—direction BI

(2) Create action

neutron policy-action-create allow—action-type allow

(3) Create rule

neutron policy-rule-create allow-multicast—classifier Multicast—actionallow

(4) Create contract

neutron contract-create Multicast-contract—policy-rules allow-multicast

(5) Create USG providing the Contract

neutron usg-create 225.1.1.1—provides-contract Multicast-Contract

neutron use-create subnet 1 USG—consumed-contract Multicast-Contract

(6) Create User in subnet 1 USG

neutron us-create us1-usg subnet 1 USG

neutron us-create us2-usg subnet 1 USG

neutron us-create us3-usg subnet 1 USG

neutron us-create us4-usg subnet 1 USG

2. The NaaS device obtains information about a network device group.

For example, that the NaaS device obtains information about a networkdevice group may include: The NaaS device obtains a fifth device groupcorresponding to the subnet 1 USG, where the fifth device group includesa device that communicates with the device group identified by thesubnet 1 USG; the NaaS device selects a seventh device from the fifthdevice group according to a condition, where the seventh devicecommunicates with the device group identified by the fourth identifier;and the NaaS device obtains information about the seventh device.Alternatively, that the NaaS device obtains information about a networkdevice group may include: the NaaS device reads a locally saved fifthdevice group; the NaaS device may traverse the fifth device group, andselect, from the fifth device group, a seventh device that meets thesubnet 1 USG and a condition; and the NaaS device obtains informationabout the seventh device. The fifth device group belongs to a candidatedevice group, and the seventh device belongs to the network devicegroup.

For example, the NaaS device may obtain the fifth device group accordingto the subnet 1 USG. The fifth device group may include forwardingdevices R1 and R2 in the network shown in FIG. 6, or the fifth devicegroup may include forwarding devices R1, R2, R3 and R4 in the networkshown in FIG. 6, or the fifth device group may include all devices inthe network shown in FIG. 6. In this embodiment of the presentapplication, composition of the fifth device group may be notspecifically limited, and in this embodiment of the present application,the fifth device group includes at least a device that can communicatewith the device group identified by the subnet 1 USG.

After obtaining the fifth device group, the NaaS device may select theseventh device from the fifth device group according to the condition.For a manner in which the NaaS device selects the seventh device, referto the implementation manner for selecting a first device in Embodiment1, and details are not described herein. For example, the NaaS devicemay obtain an identifier of the seventh device and an interface of theseventh device, and use the obtained identifier and interface as theinformation about the seventh device. For example, with reference to anetwork shown in FIG. 7, the information about the seventh device (node,interface) may be denoted as: (R1, interface2), (R1, interface1), (R1,interface3), and (R2, interface1).

3. The NaaS device obtains a first forwarding rule.

For example, that the NaaS device obtains a first forwarding rule mayinclude: The NaaS device obtains a third match field and a third actionfrom the condition, where the third match field corresponds to acommunication requirement for the device group identified by the fourthidentifier to join the multicast group identified by the fifthidentifier, and the third action corresponds to a multicast operation;and the NaaS device generates a forwarding rule of the seventh deviceaccording to the third match field and the third action.

For example, the third match field corresponds to the condition in themulticast contract, and may include an address of a multicast group, forexample, an address of a multicast group being 225.1.1.1. The thirdaction corresponds to a multicast operation, and may include joining amulticast group or exiting a multicast group.

For example, the forwarding rule of the seventh device may be denoted asa multicast enabling configuration. The forwarding rule of the seventhdevice may include a forwarding rule for R1 and a forwarding rule forR2. The forwarding rule for R1 may be denoted as: enabling a multicastfunction on R1, and statically adding R1 to a multicast group 225.1.1.1;the forwarding rule for R2 may be: enabling a multicast function on R2,and statically adding R2 to a multicast group 225.1.1.1. Optionally, theforwarding rule for R1 may be further denoted as: enabling a multicastfunction on R1, enabling a protocol independent multicast-sparse mode(PIM-SM) function on interfaces 1, 2, 3, and 4, enabling an InternetGroup Management Protocol (IGMP) function on interfaces 1, 2, and 3connected to terminals, and statically adding the interfaces 1, 2, and 3of R1 to a multicast group 225.1.1.1; the forwarding rule for R2 may befurther denoted as: enabling a multicast function on R2, enabling aPIM-SM function on the interfaces 1 and 3, enabling an IGMP function onthe interface1 connected to a terminal, and statically adding theinterface1 of R2 to a multicast group 225.1.1.1.

4. The NaaS device delivers the first forwarding rule and theinformation about the network device group to a Controller.

In this example, (node, interface, rule, action) delivered by the NaaSdevice to the Controller may be denoted as (R1; interface2; enable amulticast function on R1, and statically add R1 to a multicast group225.1.1.1; join multicast group), (R1; interface1; enable a multicastfunction on R1, and statically add R1 to a multicast group 225.1.1.1;join multicast group), (R1; interface3; enable a multicast function onR1, and statically add R1 to a multicast group 225.1.1.1; join multicastgroup), and (R2; interface1; enable a multicast function on R2, andstatically add R2 to a multicast group 225.1.1.1; join multicast group).The join multicast group denotes joining a multicast group.

Optionally, after obtaining the forwarding rule of the seventh device,the NaaS device may further perform a rule check on the obtainedforwarding rule of the seventh device. For example, in this embodimentof the present application, the rule check may be performed on theforwarding rule of the seventh device in the following twoimplementation manners.

In a first implementation manner, the NaaS device performs a rule checkon the forwarding rule of the seventh device. The performing a rulecheck on the forwarding rule of the seventh device may be performing arule check on the seventh device, or performing a rule check between theseventh device and another device in the fifth device group.

(1) The performing a rule check on the seventh device includes:

The NaaS device performs a conflict check on the forwarding rule of theseventh device and an eighth forwarding rule, where the eighthforwarding rule is a forwarding rule that is already configured on theseventh device. If a conflict exists, that is, the forwarding rule ofthe seventh device does not pass the rule check, the NaaS device obtainsa calibrated forwarding rule of the seventh device, and sends thecalibrated forwarding rule of the seventh device and the informationabout the seventh device to the Controller. If a conflict does notexist, that is, the forwarding rule of the seventh device passes therule check, the NaaS device sends the forwarding rule of the seventhdevice and the information about the seventh device to the Controller.

(2) The performing a rule check between the seventh device and anotherdevice in the fifth device group includes:

The NaaS device determines whether the forwarding rule of the seventhdevice and a forwarding rule of an eighth device in the fifth devicegroup form a transmission abnormality. If a transmission abnormality isformed, the NaaS device obtains a ninth forwarding rule, and the NaaSdevice sends the forwarding rule of the seventh device and theinformation about the seventh device to the Controller. If notransmission abnormality is formed, the NaaS device sends the forwardingrule of the seventh device and the information about the seventh deviceto the Controller. For example, the ninth forwarding rule may be acalibrated forwarding rule of the eighth device. For example, the NaaSdevice may calibrate the forwarding rule of the eighth device, to obtaina calibrated forwarding rule of the eighth device. The eighth device maydirectly communicate with the seventh device, or the eighth device mayindirectly communicate with the seventh device.

For example, the transmission abnormality may be a case such as a loopor a blackhole because of which a packet cannot be correctly forwardedto a destination node. For a manner for detecting a transmissionabnormality, refer to the foregoing process of performing loop detectionand blackhole detection in the second device group, and details are notdescribed herein.

In a second implementation manner, the NaaS device performs an actualtest on service running of a device in a physical network by using theforwarding rule of the seventh device, to discover a service abnormalityor perform fault location.

In an example, in this embodiment of the present application, an actualtest may be at least embodied as at least one of the following threeaspects: rule validity, connectivity, or QoS. For a process of an actualtest, refer to the implementation manner of the actual test inEmbodiment 1 above, and details are not described herein.

Optionally, after obtaining a detection result, the NaaS device mayfurther perform associated processing on the multicast contract by usingthe detection result and a preset condition. For a method by using whichthe NaaS device performs associated processing on the multicastcontract, refer to the implementation manner of associated processing inEmbodiment 1, and details are not described herein.

Optionally, in the foregoing embodiments of the present application, ifthe contract further includes a service type, after receiving thecontract, the NaaS device may determine a type of the contract accordingto a type identified by the service type. For example, if the servicetype is access, and the contract is an access contract; if the servicetype is routing, and the contract is a routing contract; and if theservice type is multicast, and the contract is the multicast contract.The service type may be further another extendable type, and details arenot described herein example by example.

Corresponding to the method in FIG. 1, an embodiment of the presentapplication further provides an apparatus for configuring a service. Theapparatus for configuring a service may be disposed on an Naas device ora Controller, or may be disposed on another device, and details are notdescribed herein example by example. The apparatus for configuring aservice may execute the method provided in any one of the embodimentscorresponding to FIG. 1 to FIG. 6. As shown in FIG. 7, the apparatus mayinclude:

a contract obtaining unit 201, configured to obtain a contract of aservice, where the contract includes identifier information and acondition, the identifier information is used to identify a first devicegroup, the first device group includes a device that provides theservice, and the condition is a communication requirement correspondingto the service;

a network device group obtaining unit 202, configured to obtaininformation about a network device group according to the identifierinformation and the condition;

a rule obtaining unit 203, configured to obtain a first forwarding ruleaccording to the condition, where the first forwarding rule correspondsto the network device group; and

a first sending unit 204, configured to send the first forwarding ruleand the information about the network device group to a controller.

Optionally, the identifier information is a first identifier, and thecondition is a communication requirement for accessing a device groupidentified by the first identifier;

the network device group obtaining unit is specifically configured toobtain a second device group corresponding to the first identifier,where the second device group includes a device that meets thecommunication requirement;

the network device group obtaining unit is specifically configured toselect a first device from the second device group according to thecommunication requirement for accessing the device group identified bythe first identifier; and

the network device group obtaining unit is specifically configured toobtain information about the first device, where the information aboutthe first device includes an identifier of the first device and aninterface of the first device.

Optionally, the rule obtaining unit is specifically configured to obtaina first match field and a first action from the condition, where thefirst match field corresponds to the communication requirement foraccessing the device group identified by the first identifier, and thefirst action corresponds to an access operation; and

the rule obtaining unit is specifically configured to generate aforwarding rule of the first device according to the first match fieldand the first action.

Optionally, the rule obtaining unit is further configured to perform aconflict check on the forwarding rule of the first device and a secondforwarding rule, where the second forwarding rule is a forwarding rulethat is already configured on the first device; and

if the forwarding rule of the first device conflicts with the secondforwarding rule, the rule obtaining unit is configured to calibrate theforwarding rule of the first device, to obtain a calibrated forwardingrule of the first device.

Optionally, the rule obtaining unit is further configured to determinewhether the forwarding rule of the first device and a forwarding rule ofa second device in the second device group form a transmissionabnormality; and

if the forwarding rule of the first device and the forwarding rule ofthe second device in the second device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a thirdforwarding rule, where the third forwarding rule is a forwarding ruleobtained after the forwarding rule of the second device is calibrated.

Optionally, the identifier information includes a second identifier anda third identifier, and the condition is a requirement on communicationbetween a device group identified by the second identifier and a devicegroup identified by the third identifier;

the network device group obtaining unit is specifically configured toobtain a third device group corresponding to the second identifier and afourth device group corresponding to the third identifier, where thethird device group includes a device used as a source node, and thefourth device group includes a device used as a destination node;

the network device group obtaining unit is specifically configured toselect a third device from the third device group according to therequirement on communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier, where the third device is the source node;

the network device group obtaining unit is specifically configured toselect a fourth device from the fourth device group according to therequirement on communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier, where the fourth device is the destination node; and

the network device group obtaining unit is specifically configured toobtain information about the third device and information about thefourth device, where the information about the third device includes anidentifier of the third device and an interface of the third device, andthe information about the fourth device includes an identifier of thefourth device and an interface of the fourth device.

Optionally, the rule obtaining unit is specifically configured to obtaina second match field and a second action from the condition, where thesecond match field corresponds to the requirement on communicationbetween the device group identified by the second identifier and thedevice group identified by the third identifier, and the second actioncorresponds to communication between the device group identified by thesecond identifier and the device group identified by the thirdidentifier; and

the rule obtaining unit is specifically configured to generate aforwarding rule of the third device and a forwarding rule of the fourthdevice according to the second match field and the second action.

Optionally, the rule obtaining unit is further configured to perform aconflict check on the forwarding rule of the third device and a fourthforwarding rule, where the fourth forwarding rule is a forwarding rulethat is already configured on the third device; and

if the forwarding rule of the third device conflicts with the fourthforwarding rule, the rule obtaining unit is configured to calibrate theforwarding rule of the third device, to obtain a calibrated forwardingrule of the third device.

Optionally, the rule obtaining unit is further configured to perform aconflict check on the forwarding rule of the fourth device and a fifthforwarding rule, where the fifth forwarding rule is a forwarding rulethat is already configured on the fourth device; and

if the forwarding rule of the fourth device conflicts with the fifthforwarding rule, the rule obtaining unit is configured to calibrate theforwarding rule of the fourth device, to obtain a calibrated forwardingrule of the fourth device.

Optionally, the rule obtaining unit is further configured to determinewhether the forwarding rule of the third device and a forwarding rule ofa fifth device in the third device group form a transmissionabnormality; and

if the forwarding rule of the third device and the forwarding rule ofthe fifth device in the third device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a sixthforwarding rule, where the sixth forwarding rule is a forwarding ruleobtained after the forwarding rule of the fifth device is calibrated.

Optionally, the rule obtaining unit is further configured to determinewhether the forwarding rule of the fourth device and a forwarding ruleof a sixth device in the fourth device group form a transmissionabnormality; and

if the forwarding rule of the fourth device and the forwarding rule ofthe sixth device in the fourth device group form a transmissionabnormality, the rule obtaining unit obtains a seventh forwarding rule,where the seventh forwarding rule is a forwarding rule obtained afterthe forwarding rule of the sixth device is calibrated.

Optionally, the identifier information is a fourth identifier and afifth identifier, and the condition is a communication requirement for adevice group identified by the fourth identifier to join a multicastgroup identified by the fifth identifier;

the network device group obtaining unit is specifically configured toobtain a fifth device group corresponding to the fourth identifier,where the fifth device group includes a device that communicates with adevice identified by the fourth identifier;

the network device group obtaining unit is specifically configured toselect a seventh device from the fifth device group according to thecommunication requirement for the device group identified by the fourthidentifier to join the multicast group identified by the fifthidentifier, where the seventh device communicates with the device groupidentified by the fourth identifier; and

the network device group obtaining unit is specifically configured toobtain information about the seventh device, where the information aboutthe seventh device includes an identifier of the seventh device and aninterface of the seventh device.

Optionally, the rule obtaining unit is specifically configured to obtaina third match field and a third action from the condition, where thethird match field corresponds to the communication requirement for thedevice group identified by the fourth identifier to join the multicastgroup identified by the fifth identifier, and the third actioncorresponds to a multicast operation; and

the rule obtaining unit is specifically configured to generate aforwarding rule of the seventh device according to the third match fieldand the third action.

Optionally, the rule obtaining unit is further configured to perform aconflict check on the forwarding rule of the seventh device and aneighth forwarding rule, where the eighth forwarding rule is a forwardingrule that is already configured on the seventh device; and

if the forwarding rule of the seventh device conflicts with the eighthforwarding rule, the rule obtaining unit is configured to calibrate theforwarding rule of the seventh device, to obtain a calibrated forwardingrule of the seventh device.

Optionally, the rule obtaining unit is further configured to determinewhether the forwarding rule of the seventh device and a forwarding ruleof an eighth device in the fifth device group form a transmissionabnormality; and

if the forwarding rule of the seventh device and the forwarding rule ofthe eighth device in the fifth device group form a transmissionabnormality, the rule obtaining unit is configured to obtain a ninthforwarding rule, where the ninth forwarding rule is a forwarding ruleobtained after the forwarding rule of the eighth device is calibrated.

Optionally, the apparatus further includes:

a detection packet obtaining unit, configured to obtain a detectionpacket according to the first forwarding rule and the information aboutthe network device group, where the detection packet is used to obtain adetection result from the network device group, and the detection resultis a result of communication that is performed by the network devicegroup according to the first forwarding rule;

a second sending unit, configured to send the detection packet to thecontroller;

a receiving unit, configured to receive the detection result sent by thecontroller; and

an adjustment unit, configured to adjust the contract according to thedetection result when the detection result meets a preset condition.

Optionally, the contract further includes a type of the service, and thetype of the service is access, routing, or multicast.

Correspondingly, an embodiment of the present application furtherprovides an apparatus for configuring a service. The apparatus forconfiguring a service may be disposed on an Naas device or a Controller,or may be disposed on another device, and details are not describedherein example by example. The apparatus for configuring a service mayexecute the method provided in any one of the embodiments correspondingto FIG. 1 to FIG. 6. As shown in FIG. 8, the apparatus for configuring aservice may include: a processor 301, a memory 302, and a communicationsinterface 303. The processor 301, the memory 302, and the communicationsinterface 303 may be connected by using a communications bus 304. Thememory 302 is configured to store a program, and the processor 301executes a specific operation according to an executable instructionincluded in the program read from the memory 302.

Optionally, the contract obtaining unit 201 and the first sending unit204 in FIG. 7 may be implemented by the communications interface 303 inFIG. 8, and the communications interface 303 may include at least onephysical interface. The network device group obtaining unit 202 and therule obtaining unit 203 in FIG. 7 may be implemented by the processor301 in FIG. 8 according to the executable instruction stored in thememory 302, and the processor 301 may include at least one physicalprocessor.

Optionally, the second sending unit and the receiving unit in theembodiment corresponding to FIG. 7 may also be implemented by thecommunications interface 303 in FIG. 8. The detection packet obtainingunit and the adjustment unit in the embodiment corresponding to FIG. 7may also be implemented by the processor 301 in FIG. 8 according to theexecutable instruction stored in the memory 302.

It should be noted that, the apparatus, shown in FIG. 7, for configuringa service and the apparatus, shown in FIG. 8, for configuring a servicemay be a same apparatus, and it may be considered that FIG. 8 shows,from a physical perspective, content included in an apparatus forconfiguring a service, and FIG. 7 shows, from a logic perspective,content included in an apparatus for configuring a service.

In the apparatus, shown in FIG. 8, for configuring a service, theprocessor 301 is configured to read the instruction and data stored inthe memory 302 to perform the following operations:

obtaining, by the processor 301, a contract of a service by using thecommunications interface 303, where the contract includes identifierinformation and a condition, the identifier information is used toidentify a first device group, the first device group includes a devicethat provides the service, and the condition is a communicationrequirement corresponding to the service;

obtaining, by the processor 301, information about a network devicegroup according to the identifier information and the condition;

obtaining, by the processor 301, a first forwarding rule according tothe condition, where the first forwarding rule corresponds to thenetwork device group; and

sending, by the processor 301, the first forwarding rule and theinformation about the network device group to a controller by using thecommunications interface 303.

Based on the foregoing descriptions of the implementation manners, aperson skilled in the art may clearly understand that all or some stepsof the methods in the foregoing embodiments may be implemented bysoftware in addition to a general hardware platform.

Based on such an understanding, the technical solutions of the presentapplication essentially or the part contributing to the prior art may beimplemented in a form of a software product. The computer softwareproduct may be stored in a storage medium, such as a read-only memory(ROM), a random access memory (RAM), a magnetic disk, or an opticaldisc, and includes several instructions for instructing a computerdevice (which may be a personal computer, a server, a networkcommunications device such as media gateway, or the like) to perform themethods described in the embodiments or some parts of the embodiments ofthe present application.

It should be noted that the embodiments in this specification are alldescribed in a progressive manner, for same or similar parts in theembodiments, reference may be made to these embodiments, and eachembodiment focuses on a difference from other embodiments. Especially,device and system embodiments are basically similar to a methodembodiment, and therefore are described briefly; for related parts,reference may be made to partial descriptions in the method embodiment.The described device and system embodiments are merely exemplary. Theunits described as separate parts may or may not be physically separate,and parts displayed as units may or may not be physical units, may belocated in one position, or may be distributed on a plurality of networkunits. Some or all of the modules may be selected according to actualrequirements to achieve the objectives of the solutions of theembodiments. A person of ordinary skill in the art may understand andimplement the embodiments of the present application without creativeefforts.

The foregoing descriptions are merely optional implementation manners ofthe present application, but are not intended to limit the protectionscope of the present application. It should be noted that a person ofordinary skill in the art may make some improvements and polishingwithout departing from the principle of the present application and theimprovements and polishing shall fall within the protection scope of thepresent application.

What is claimed is:
 1. A method for configuring a service, comprising:obtaining identifier information and a condition, wherein the identifierinformation is used to identify a first device group, the first devicegroup comprises a device that provides a service, and the condition is acommunication requirement corresponding to the service; obtaininginformation about a network device group according to the identifierinformation and the condition, wherein the network device groupcomprises a network device satisfying the condition; obtaining a firstforwarding rule according to the condition, wherein the first forwardingrule corresponds to the network device group, and the first forwardingrule is used to enable the network device in the network device group toprovide the service to the device in the first device group; and sendingthe first forwarding rule.
 2. The method according to claim 1, whereinthe identifier information comprises a first identifier, the conditioncomprises a communication requirement for accessing a device groupidentified by the first identifier, and the obtaining information abouta network device further comprises: determining a second device groupcorresponding to the first identifier, wherein the second device groupis a backup device group and the second device group comprises a firstdevice, and the first device is a device that meets the communicationrequirement; selecting the first device from the second device groupaccording to the communication requirement for accessing the devicegroup identified by the first identifier; and obtaining informationabout the first device, wherein the information about the first devicecomprises an identifier of the first device and an interface of thefirst device.
 3. The method according to claim 2, wherein the obtaininga first forwarding rule according to the condition further comprises:obtaining a first match field and a first action from the condition,wherein the first match field corresponds to the communicationrequirement for accessing the device group identified by the firstidentifier, and the first action corresponds to an access operation; andgenerating a forwarding rule of the first device according to the firstmatch field and the first action.
 4. The method according to claim 3,wherein the obtaining a first forwarding rule according to the conditionfurther comprises one or more of: when the forwarding rule of the firstdevice conflicts with the second forwarding rule, obtaining a calibratedforwarding rule of the first device; and when the forwarding rule of thefirst device and the forwarding rule of the second device in the seconddevice group form a transmission abnormality, obtaining a thirdforwarding rule, wherein the third forwarding rule is a calibratedforwarding rule of the second device.
 5. The method according to claim1, wherein the identifier information comprises a fourth identifier anda fifth identifier, the condition comprises a communication requirementfor a device group identified by the fourth identifier to join amulticast group identified by the fifth identifier, and the obtaininginformation about a network device group according to the identifierinformation and the condition further comprises: determining a fifthdevice group corresponding to the fourth identifier, wherein the fifthdevice group comprises a device that communicates with a deviceidentified by the fourth identifier; selecting a seventh device from thefifth device group according to the communication requirement for thedevice group identified by the fourth identifier to join the multicastgroup identified by the fifth identifier, wherein the seventh devicecommunicates with the device group identified by the fourth identifier;and obtaining information about the seventh device, wherein theinformation about the seventh device comprises an identifier of theseventh device and an interface of the seventh device.
 6. The methodaccording to claim 5, wherein the obtaining a first forwarding ruleaccording to the condition further comprises: obtaining a third matchfield and a third action from the condition, wherein the third matchfield corresponds to the communication requirement for the device groupidentified by the fourth identifier to join the multicast groupidentified by the fifth identifier, and the third action corresponds toa multicast operation; and generating a forwarding rule of the seventhdevice according to the third match field and the third action;
 7. Themethod according to claim 6, wherein the obtaining a first forwardingrule according to the condition further comprises one or more of: whenthe forwarding rule of the seventh device conflicts with the eighthforwarding rule, obtaining a calibrated forwarding rule of the seventhdevice; and when a transmission abnormality is formed, obtaining a ninthforwarding rule, wherein the ninth forwarding rule is a calibratedforwarding rule of the eighth device.
 8. The method according to claim1, further comprising: obtaining a detection packet according to thefirst forwarding rule and the information about the network devicegroup, wherein the detection packet is used to obtain a detection resultfrom the network device group, and the detection result is a resultobtained by detecting communication that is performed by the networkdevice group according to the first forwarding rule; sending thedetection packet to a controller; receiving the detection result sent bythe controller; and when the detection result meets a preset condition,adjusting the contract according to the detection result.
 9. The methodaccording to claim 1, wherein the contract further comprises a type ofthe service, and the type of the service comprises access, routing, ormulticast.
 10. The method according to claim 1, wherein the method isperformed by a network as a service (NaaS) device.
 11. An apparatus,wherein the apparatus having a network as a service (NaaS) functioncomprises a processor configured to execute instructions to: obtainidentifier information and a condition, wherein the identifierinformation is used to identify a first device group, the first devicegroup comprises a device that provides a service, and the condition is acommunication requirement corresponding to the service; obtaininformation about a network device group according to the identifierinformation and the condition, wherein the network device groupcomprises a network device satisfying the condition; obtain a firstforwarding rule according to the condition, wherein the first forwardingrule corresponds to the network device group, and the first forwardingrule is used to enable the network device in the network device group toprovide the service to the device in the first device group; and sendthe first forwarding rule.
 12. The apparatus according to claim 11,where the identifier information comprises a first identifier, thecondition comprises a communication requirement for accessing a devicegroup identified by the first identifier, and the processor executes theinstructions to: determine a second device group corresponding to thefirst identifier, wherein the second device group is a backup devicegroup and the second device group comprises a first device, and thefirst device is a device that meets the communication requirement;select the first device from the second device group according to thecommunication requirement for accessing the device group identified bythe first identifier; and obtain information about the first device,wherein the information about the first device comprises an identifierof the first device and an interface of the first device.
 13. Theapparatus according to claim 12, where the processor executes theinstructions to: obtain a first match field and a first action from thecondition, wherein the first match field corresponds to thecommunication requirement for accessing the device group identified bythe first identifier, and the first action corresponds to an accessoperation; and generate a forwarding rule of the first device accordingto the first match field and the first action.
 14. The apparatusaccording to claim 13, where the processor further executes theinstructions to perform one or more of: when the forwarding rule of thefirst device conflicts with the second forwarding rule, obtaining acalibrated forwarding rule of the first device; and when the forwardingrule of the first device and the forwarding rule of the second device inthe second device group form a transmission abnormality, obtaining athird forwarding rule, wherein the third forwarding rule is a calibratedforwarding rule of the second device.
 15. The apparatus according toclaim 11, wherein the identifier information comprises a fourthidentifier and a fifth identifier, the condition comprises acommunication requirement for a device group identified by the fourthidentifier to join a multicast group identified by the fifth identifier,and where the processor executes the instructions to: determining afifth device group corresponding to the fourth identifier, wherein thefifth device group comprises a device that communicates with a deviceidentified by the fourth identifier; selecting a seventh device from thefifth device group according to the communication requirement for thedevice group identified by the fourth identifier to join the multicastgroup identified by the fifth identifier, wherein the seventh devicecommunicates with the device group identified by the fourth identifier;and obtaining information about the seventh device, wherein theinformation about the seventh device comprises an identifier of theseventh device and an interface of the seventh device.
 16. The apparatusaccording to claim 15, where the processor executes the instructions to:obtain a third match field and a third action from the condition,wherein the third match field corresponds to the communicationrequirement for the device group identified by the fourth identifier tojoin the multicast group identified by the fifth identifier, and thethird action corresponds to a multicast operation; and generate aforwarding rule of the seventh device according to the third match fieldand the third action;
 17. The apparatus according to claim 16, where theprocessor further executes the instructions to perform one or more of:when the forwarding rule of the seventh device conflicts with the eighthforwarding rule, obtaining a calibrated forwarding rule of the seventhdevice; and when a transmission abnormality is formed, obtaining a ninthforwarding rule, wherein the ninth forwarding rule is a calibratedforwarding rule of the eighth device.
 18. The apparatus according toclaim 11, where the processor further executes the instructions to:obtain a detection packet according to the first forwarding rule and theinformation about the network device group, wherein the detection packetis used to obtain a detection result from the network device group, andthe detection result is a result obtained by detecting communicationthat is performed by the network device group according to the firstforwarding rule; send the detection packet to a controller; receive thedetection result sent by the controller; and when the detection resultmeets a preset condition, adjust the contract according to the detectionresult.
 19. The apparatus according to claim 11, wherein the contractfurther comprises a type of the service, and the type of the servicecomprises access, routing, or multicast.
 20. A network system comprisingan apparatus having a network as a service (NaaS) function, where theapparatus comprises a processor configured to execute instructions to:obtain identifier information and a condition, wherein the identifierinformation is used to identify a first device group, the first devicegroup comprises a device that provides a service, and the condition is acommunication requirement corresponding to the service; obtaininformation about a network device group according to the identifierinformation and the condition, wherein the network device groupcomprises a network device satisfying the condition; obtain a firstforwarding rule according to the condition, wherein the first forwardingrule corresponds to the network device group, and the first forwardingrule is used to enable the network device in the network device group toprovide the service to the device in the first device group; and sendthe first forwarding rule.